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.
Difference between revisions of "EclipseLink/Development/JPA"
(→Development Approach) |
m (→Development Approach) |
||
| Line 14: | Line 14: | ||
== Development Approach == | == Development Approach == | ||
| − | In order to support JPA 2.0 new capabilities will be added to | + | In order to support JPA 2.0 new capabilities will be added to EclipseLink's core object-relational foundation. These features will then be exposed through new JPA 2.0 metadata and corresponding processing. the goal is to first make these available and functional in the native API so that all object-relational consumers have access and to minimize JPA only capabilities. JPA is definitely the priority but by making the features available internally we can more easily proceed with development of JPA 2.0 related functionality without requiring a final specification defintion of the metadata or having to deal with to much flux as the metadata approach evolves in the expert group. |
=== Metadata Changes === | === Metadata Changes === | ||
Revision as of 12:44, 17 December 2007
Developing the functionality required for JPA 2.0 will involve careful planning in order to maintain compatibility with JPA 1.0 interfaces and annotations.
Contents
Types of Changes
- Metadata Changes
- New Annotations
- New structures in the persistence.xml XSD
- New structures in the ORM.XML XSD
- API Changes
- New interfaces
- New methods on existing interfaces
- Changes to existing methods
Development Approach
In order to support JPA 2.0 new capabilities will be added to EclipseLink's core object-relational foundation. These features will then be exposed through new JPA 2.0 metadata and corresponding processing. the goal is to first make these available and functional in the native API so that all object-relational consumers have access and to minimize JPA only capabilities. JPA is definitely the priority but by making the features available internally we can more easily proceed with development of JPA 2.0 related functionality without requiring a final specification defintion of the metadata or having to deal with to much flux as the metadata approach evolves in the expert group.
Metadata Changes
API Changes
javax.persistence.EntityManager
Can we add API to org.eclipse.persistence.jpa.JpaEntityManager aligning with JPA 2.0 proposed API so that we can maintain support for JPA 1.0's EntityManager?
JPA 2.0 Features
the following are the features known to be required for JPA 2.0: