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/Examples/JPA/Dynamic
< EclipseLink | Examples | JPA
Revision as of 12:49, 2 April 2008 by Douglas.clarke.oracle.com (Talk | contribs) (→Download and Running)
 | This page is under construction. See bug 225026 for more information |
Contents
How to use dynamic JPA persistence
This how-to illustrates how EclipseLink can be extended to deliver all of its JPA functionality in a dynamic scenario where no Java class exists for the entity and optionally where no XML is provided. This allows the EclipseLink JPA solution to be used in more dynamic environments where either the mode is unknown at development time or the application is simply dynamic in nature.
Dynamic Entity Extension
Example
The dynamic entity extension is currently illustrated through test cases in the example.
Try It Out
TBD
Outstanding Work
This how-to is based on an extension to EclipseLink JPA. The functionality needs to be consolidated into the project leveraging the existing dynamic support introduced in EclipseLink SDO.
TO DO:
- Add support for using JPA ORM.XML and EclipseLink ORM.XML. At present the metadata processor always validates the existence of the field or standard get method on the class.
- Consolidate the SDO approach for a base dynamic entity class with this one in the Foundation component
- Minimize the introduction of yet another meta model. This will be done either through usage of the existing Descriptor/Mapping model or through some generalization of the SDO meta-model basics within Foundation.