Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/2.2"

(Metadata)
 
(3 intermediate revisions by 3 users not shown)
Line 18: Line 18:
 
=== Metadata ===
 
=== Metadata ===
  
Continue to expand content of eclispelink-orm.xml and eclipselink-oxml.xml to cover more advanced functionality in an effort to eliminate the need for the native deployment xml.
+
Continue to expand content of eclipselink-orm.xml and eclipselink-oxml.xml to cover more advanced functionality in an effort to eliminate the need for the native deployment xml.
 
* MOXy: backlog of features
 
* MOXy: backlog of features
 
* JPA: backlog of features
 
* JPA: backlog of features
** [[ EclipseLink/Development/2.2/AdvancedJPA | Advanced mapping options]] available through custom annotations and/or eclispelink-orm.xml - {{bug|312910}}
+
** [[ EclipseLink/Development/2.2/AdvancedJPA | Advanced mapping options]] available through custom annotations and/or eclipselink-orm.xml - {{bug|312910}}
 
* DBWS: Switch to using these files
 
* DBWS: Switch to using these files
  
Line 28: Line 28:
 
During Object construction the shared cache is accessed frequently. With CacheInterceptors allowing remote caching technologies the access to the shared cache needs to be minimized.
 
During Object construction the shared cache is accessed frequently. With CacheInterceptors allowing remote caching technologies the access to the shared cache needs to be minimized.
  
=== Audit/History ===
+
=== Design Documents ===
 
+
See,
Currently EclipseLink offers a history solution which addresses storing previous versions of rows as they are modified and offering point-in-time querying to see entities and their relationships as they appeared at that time. In this release we hope to expand this support addressing several items.
+
[[EclipseLink/Development/DesignDocs#EclipseLink_2.2]]
 
+
* JPA enabling of the support
+
** As-Of EntityManager (read-only)
+
* Bi-temporal/future version
+
* Usage with auditing
+
  
 
== Schedule==
 
== Schedule==
 
* 2.2M1 - July?
 
* 2.2M2 - August?
 
* 2.2M3 - September?
 
* 2.2M4 - October?
 
* IPLog and Release docuware - end of October
 
* 2.2RC1 - November 3rd, 2010
 
* 2.2RC2 - November 17th, 2010
 
* 2.2RC3 - Novemeber 24th, 2010
 
* 2.2 Release - December 8th, 2010
 

Latest revision as of 10:59, 16 June 2011

EclipseLink 2.2 Release Planning

Themes

Community

Catch up on bug backlog focusing on bugs with votes, submitted patches, and non-committer filed bugs

Platforms

  • Add MAXDB platform

Metadata

Continue to expand content of eclipselink-orm.xml and eclipselink-oxml.xml to cover more advanced functionality in an effort to eliminate the need for the native deployment xml.

  • MOXy: backlog of features
  • JPA: backlog of features
  • DBWS: Switch to using these files

Optimizing Cache Usage

During Object construction the shared cache is accessed frequently. With CacheInterceptors allowing remote caching technologies the access to the shared cache needs to be minimized.

Design Documents

See, EclipseLink/Development/DesignDocs#EclipseLink_2.2

Schedule

Back to the top