Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/Dynamic"

Line 2: Line 2:
 
<table border="0" cellpadding="5" align="center"><tr><td width="20">[[image:Catnicon.gif]]</td><td>This page is under construction. See bug [http://bugs.eclipse.org/225026 225026] for more information</td></tr></table>
 
<table border="0" cellpadding="5" align="center"><tr><td width="20">[[image:Catnicon.gif]]</td><td>This page is under construction. See bug [http://bugs.eclipse.org/225026 225026] for more information</td></tr></table>
 
</div>
 
</div>
 +
 +
= 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.
 +
 +
 +
 +
== Download and Running ==
 +
 +
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.

Revision as of 11:49, 2 April 2008

Catnicon.gifThis page is under construction. See bug 225026 for more information

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.


Download and Running

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.