Difference between revisions of "EclipseLink/Development/2.1"
|Line 86:||Line 86:|
| M1 || ? ||
| M1 || ? || || Target for Helios M4
Revision as of 09:05, 16 December 2009
EclipseLink 2.1 (Helios) Planning
Target Release Date: Helios (June 23, 2010)
The following themes are being addressed for the 2.1 release with all feature working falling within these themes.
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.
Will we be shipping Modelgen with Helios? This opens the question of whether Modelgen needs to be OSGi (if it ships it does) and if we will begin work to integrate modelgen with eclipse, or if we will be assisting Dali with any required integration.
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.
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.
- TODO - Add Bug Query
In the 2.1 release the project is planning to increase the advanced native features available through standard API using common extension points, custom annotations, and extended XML configuration files. The goal is to enable users to work with the standards (JPA, JAXB, SDO) as much as possible and simplify the usage of advanced features.
- Advanced JPA
- Advanced mapping options available through custom annotations and/or eclispelink-orm.xml
- Query Extensions available through JPQL and Criteria API
- Advanced MOXy (JAXB)
- Complete JAXB mapping support in eclipselink-oxm.xml mapping file
- Advanced mapping options available through custom annotations and/or eclispelink-oxm.xml
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.
- Root Dynamic Bug
Based on the above theme the following requirements will be addressed for this release.
|Helios-1||All||Meet Helios release train requirements||?|
|Helios-2||JPA||Upgrade weaving support to use Equinox Weaving||?|
|Community-1||All|| Reduce Bug/ER backlog
Backlog will be addressed based on priority, votes, patches supplied, and feasibility for the release time frame.
|Community-2||JPA|| Deliver new EclipseLink JPA documentation.
The goal is to deliver version specific content that is easier to use and consume.
|Metadata-1||JPA||Provide access to all functionality from deployment XML in eclipselink-orm.xsd (bug 227219)||?|
|Metadata-2||MOXy||Provide access to all functionality from deployment XML in eclipselink-oxm.xsd (bug 293925)||?|
|Metadata-3||JPA/MOXy||Have the workbench generate eclipselink-orm and eclipselink-oxm as well as migrating from deployment XML|
|Advanced-1||JPA||Extended JPA querying to support (JPQL (bug 219814) & Criteria)||?|
|Dynamic-1||JPA||Enable dynamic JPA using eclipselink-orm.xsd||?|
|Dynamic-2||MOXy||Enable dynamic MOXy using eclipselink-oxm.xsd and API (bug 296967)||?|
|Dynamic-3||JPA/MOXy||Enable dynamic models using both JPA and MOXy using XML and/or API configuration||?|
The 2.1 development and release schedule must align with the Helios schedule.
|M1||?||Building||Target for Helios M4|