Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/DesignDocs/214661
Functional Specification: VM managed Entity detachment
Document History
Date | Author | Version Description & Notes
} Project overviewAllowing a Persistence Context to reference managed objects in a weak manner would provide Rich Clients an automatic memory management mechanism. Currently JPA clients must manage memory foot print manually by controlling the lifetime of the PersistenceContext as well as the contents of the Persistence Context. Within a Rich Client environment it is much easier for application developers to simply use the managed objects as the UI backing objects and leverage transparent persistence instead of creating a DOA layer. Currently the only limitation with this approach is memory management. Persistence Contexts tend to grow and detaching objects is problematic. With this feature memory management can be delegated to the VMs garbage collection functionality through the use of weak references. End users must be aware of certain side effects of unpredictable detachment from the Persistence Context but as long as developers are aware of the limitations the feature should provide the needed functionality. Goals: ConceptsRequirementsFunctionalityDesign ConstraintsMaintainabilityGUIConfig filesDocumentationOpen IssuesThis section lists the open issues that are still pending that must be decided prior to fully implementing this project's requirements.
|
---|