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/RoadMap"
< EclipseLink | Development
(→2.0: Fall2009) |
(→= 1.1.1 - Galileo Release Train) |
||
Line 19: | Line 19: | ||
*[[EclipseLink/Release/1.1 | Draft release notes]] | *[[EclipseLink/Release/1.1 | Draft release notes]] | ||
− | + | == 1.1.1 - Galileo Release Train == | |
* Release Train Requirements | * Release Train Requirements |
Revision as of 13:29, 13 October 2009
EclipseLink Road Map
The following are the future release plans for EclipseLink. Summary of previous releases available here.
1.1 Release: Feb 2009
- SDO 2.1.1 Compliance
- Initial release of DBWS functionality
- Data Access Service enabling SDO wrapping POJOs or JPA entities
- JPA Enhancements
- Unidirectional 1:M Mapping
- TABLE_PER_CLASS Inheritance
1.1.1 - Galileo Release Train
- Release Train Requirements
- OSGi Usage Enhancements
- Bug Fixes
EclipseLink 2.0: Fall 2009
- JPA: 2.0 Compliance
- MOXy
- Annotation support for advanced functionality
- JAXB 2.1 Certification
- SDO: Data Access Service integrating SDO with JPA
Future
The following is a list of potential future enhancements to the EclipseLink project.
- Foundation
- Extend pluggable caching to include a reference implementation
- JPA
- Replace original deployment XML with eclipselink-orm.xml - add additional advanced features
- Improve usability of native features through JPA
- Historical sessions and querying
- Migration: Improve documentation and utilities
- MOXy
- Additional annotations to expose advanced mapping capabilities
- Enhanced support for OXM.XML
- Simplify XSD
- Support usage in combination with annotations
- SDO
- DAS support for leveraging SDO Change Summary