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/2.2"
(→Themes) |
(→Audit/History) |
||
| Line 30: | Line 30: | ||
=== Audit/History === | === Audit/History === | ||
| + | |||
| + | 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. | ||
| + | |||
| + | * JPA enabling of the support | ||
| + | ** As-Of EntityManager (read-only) | ||
| + | * Bi-temporal/future version | ||
| + | * Usage with auditing | ||
Revision as of 10:33, 17 June 2010
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 eclispelink-orm.xml and eclipselink-oxml.xml to cover more advanced functioanlity 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.
JPA Query Extensions
Audit/History
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.
- JPA enabling of the support
- As-Of EntityManager (read-only)
- Bi-temporal/future version
- Usage with auditing