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"
| Line 1: | Line 1: | ||
<div style="float:right;border:1px solid #000000;padding:5px">__TOC__</div> | <div style="float:right;border:1px solid #000000;padding:5px">__TOC__</div> | ||
| − | '''PAGE STATUS: DRAFT''' | + | '''PAGE STATUS: DRAFT''' |
The EclipseLink project has been chosen to deliver the JPA 2.0 reference implementation as part of JSR 317. This page provides a summary of the work planned and the current status. | The EclipseLink project has been chosen to deliver the JPA 2.0 reference implementation as part of JSR 317. This page provides a summary of the work planned and the current status. | ||
| Line 11: | Line 11: | ||
</div> | </div> | ||
| − | == | + | == Goals/Requirements == |
| − | + | ||
| − | + | ||
| − | + | ||
EclipseLink will introduce JPA 2.0 features with the following goals in mind: | EclipseLink will introduce JPA 2.0 features with the following goals in mind: | ||
Revision as of 10:58, 26 March 2008
PAGE STATUS: DRAFT
The EclipseLink project has been chosen to deliver the JPA 2.0 reference implementation as part of JSR 317. This page provides a summary of the work planned and the current status.
JPA 2.0 Implementation Status
At present EclipseLink implements JPA 1.0 with advanced functionality made available through Persistence Unit Properties, Query Hints, a native ORM XML Schema, and native API.
Goals/Requirements
EclipseLink will introduce JPA 2.0 features with the following goals in mind:
- Remain a compliant JPA 1.0 implementation during the development of 2.0 functionality. This is a major requirement since we are working towards a 1.0 release of EclipseLink which must be JPA 1.0 compliant.
- This generally means that the JPA 1.0 persistence.jar could be on the classpath and the product should function as expected
- Conform with the Eclipse IP process and rules. This means that the use of any updated persistence libraries and their source must come into the project through proper IP review procedures.
- All new features involving changes to JPA's ORM-XML schema must be reflected in Eclipse-ORM.XML. This should be done in such a way that changes during the evolution of the specification are minimized.
- Where possible any new features added for JPA 2.0 should also be available to users of the native EclipseLink ORM API and metadata. Accessibility through the native API can be limited to programmatic access and configuration.
- EclipseLink users using JPA 1.0 will be able to access 2.0 preview functionality through native EclipseLink API or metadata
Types of Changes
The JPA 2.0 expert group is attempting to evolve this new specification to remain backwards compatible with JPA 1.0. The scope of its work will involve changes of various types with different effects on EclipseLink.
- 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
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 definition of the metadata or having to deal with too much flux as the metadata approach evolves in the expert group.
Metadata Changes
The following changes need to be handled keeping the backwards compatibility to JPA 1.0 goals in mind:
- New Annotations
- Modified Annotations
- Changes to the XML Schemas
Replacing Existing EclipseLink Annotations
Q: Are there EclipseLink JPA extension annotations that exist today that will not be required in 2.0? What is the general strategy to handle these in EclipseLink 1.0?
- @CollectionTable
JPA 2.0 Features
The following are features known to be required for JPA 2.0
Note that plumbing for some of these features already does exist in EclipseLink while other parts are going to require feature additions.
Feature placeholders:
• Nested embedding
Embedded objects can nest other embedded objects as well as being able to have relationships to entities
• New collections mappings
Collections of embedded objects (aka Aggregate Collections) or of simple objects (Direct Collections)
• Extended Map support
Maps can have keys and values that can be any of basic, entity, or embedded. These are typically stored in a separate table, etc.
• Ordered lists
Order of list is persisted to an "order column" when writes occur
• Derived identifiers
Identifiers that contain relationships can be expressed in terms of the relationships (without an additional mapped FK property in the entity)
• Mixed attribute access types
Can specify different access type for different attributes of an entity
• Orphan removal
When relationship is severed then the child is orphaned and hence deleted (other half of private-owned)
JPA 1.0 Optional Features
-- There were several optional features in JPA 1.0, are these now required?
-- James.sutherland.oracle.com 11:51, 7 January 2008 (EST)
- Table per class inheritance.
- OneToOne using a join table?
- Lazy basics.
We do not support some of these, so this needs to be taken into consideration as part of the JPA 2.0 development.