Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/DynamicOXM"
< EclipseLink | Development
(New page: <css> .source-java5 {border-style: solid;} </css> __NOTOC__ = Dynamic Persistence with EclipseLink OXM = This page provides an overview for the work done to support Dynamic Persistenc...) |
|||
| Line 21: | Line 21: | ||
|} | |} | ||
<br/> | <br/> | ||
| + | |||
| + | __TOC__ | ||
| + | |||
| + | == Overview == | ||
| + | |||
| + | The first step in creating a JPA-JAXB meet-in-the-middle solution is to enable EclipseLink OXM to use Dynamic Persistence, a.k.a. processing Projects, Mappings & Descriptors without having concrete Java classes available. This work builds off of the initial Dynamic Persistence functionality (<code>org.eclipse.persistence.dynamic</code>) current used by the JPA component. By supplying a <code>DynamicClassLoader</code> and loading the EclipseLink project by way of <code>DynamicTypeBuilder.loadDynamicProject()</code>, we can inject Dynamic Persistence functionality into EclipseLink OXM in a fairly transparent way. | ||
Revision as of 15:53, 17 November 2009
Dynamic Persistence with EclipseLink OXM
This page provides an overview for the work done to support Dynamic Persistence in EclipseLink OXM.
Document History
| Date | Author | Version Description & Notes |
|---|---|---|
| 091117 | Rick Barkhouse | 1.0 |
Overview
The first step in creating a JPA-JAXB meet-in-the-middle solution is to enable EclipseLink OXM to use Dynamic Persistence, a.k.a. processing Projects, Mappings & Descriptors without having concrete Java classes available. This work builds off of the initial Dynamic Persistence functionality (org.eclipse.persistence.dynamic) current used by the JPA component. By supplying a DynamicClassLoader and loading the EclipseLink project by way of DynamicTypeBuilder.loadDynamicProject(), we can inject Dynamic Persistence functionality into EclipseLink OXM in a fairly transparent way.