EclipseLink 2.1 (Helios) Planning
Target Release Date: Helios (June 23, 2010)
This is the EclipseLink release that will go into the annual Eclipse Helios release. Some work will be required to ensure all of the release train requirements are met and that EclipseLink functions well within the IDE as well as within the RT platform. This work will involve addressing better OSGi/Equinox compatibility.
The last couple of release cycles have had a focus on major new feature areas (SDO, DBWS, JPA 2.0). This work has prevented the project team from keeping up with the community's request for enhancements and bug fixes. This release will endeavor to reduce the bug backlog to a more reasonable quantity.
Currently the EclipseLink project offers multiple metadata approaches for each persistence service. This release will focus on simplifying around simplifying the metadata approach used for each service ensuring that all necessary functionality is available.
With the completion of the JPA 2.0 implementation focused on delivering the reference implementation the project will now work on exposing additional advanced Object-Relational features through easy to use extensions to JPA that will enable users to easily and consistently consume them with minimal dependencies on native EclipseLink API.
Continued improvements to usability focusing on simplified getting started steps as well as ability to find technical information on how EclipseLink works and how to solve both common and advanced requirements.
The 1.2.0 and 2.0.0 releases of EclipseLink introduced support for dynamic entities that could be mapped without requiring .java files being generated/compiled/packaged. This support will now be further extended to work with all of the applicable configuration models in MOxy and JPA including combining multiple mappings for the same entities. The now public infrastructure will also be coordinated with SDO and DBWS use of dynamic persistence.
Based on the above theme the following requirements will be addressed for this release.
The 2.1 development and release schedule must align with the Helios schedule.