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/Release/2.1.0"
(→OSGi and JPA) |
(→Known Issues) |
||
| Line 51: | Line 51: | ||
==Known Issues== | ==Known Issues== | ||
| − | + | The following are known issues that have been identified as potentially effecting users of EclipseLink 2.1. For a list of all open bugs and enhancement requests please see the queries at [[EclipseLink/Bugs]] | |
| − | |||
| − | + | {|{{BMTableStyle}} | |
| − | + | |-{{BMTHStyle}} | |
| − | There is a known dependency issue when building RCP applications using the <code>org.eclipse.persistence.moxy</code> bundle in combination with the <code>org.eclipse.core.runtime</code>. For more information and workarounds for this issue, please refer to | + | ! Summary |
| + | ! Details | ||
| + | |- | ||
| + | | EclipseLink JPA with OSGi | ||
| + | | In order to use EclipseLink 2.1 OSGi, you ''must'' use the '''org.eclipse.persistence.jpa''' bundle included with this release. This bundle provides support for Gemini, the reference implementation for the OSGI Java EE integration specifica | ||
| + | |- | ||
| + | | RCP Development with MOXy | ||
| + | | There is a known dependency issue when building RCP applications using the <code>org.eclipse.persistence.moxy</code> bundle in combination with the <code>org.eclipse.core.runtime</code>. For more information and workarounds for this issue, please refer to {{bug|298318}}. | ||
| + | |} | ||
== Resolved Issues == | == Resolved Issues == | ||
Revision as of 13:42, 8 June 2010
EclipseLink 2.1.0 Release Notes
The EclipseLink 2.1 (Helios) release focuses on providing advanced persistence features for user of relational, XML and Web Services to expose advanced persistence features that naturally extend the industry standards in these spaces.
Release under development see 2.1.0 Plan
Contents
Download EclipseLink 2.1.0
- Repositories
- Helios
- EclipseLink 2.1
- Maven
- Complete Install (zip)
New and Noteworthy
- JPA
- New NetWeaver Server Platform
- Advanced Querying
- Casting using TREAT AS
- Batch reading extended to add IN and EXISTS mode to JOIN
- FUNC support in criteria and JPQL to invoke database functions
- Advanced Configuration of JPA extensions using eclipselink-orm.xml files
- Extended AttributeGroup support for Fetch, Load, Copy & Merge scenarios with partial entities
- Dynamic Persistence: Bootstrap from eclipselink-orm.xml, API, or native XML
- MOXy
- JAXB 2.2 Compliance
- Advanced Configuration using eclipselink-oxm.xml to externalize JAXB and extended mappings
- Dynamic Persistence from XSD or XML config
- SDO
- Added server support for WebSphere and JBoss
- Enhanced support for local helper contexts (including Java serialization for DataObjects associated with local helper contexts).
- DBWS
- Support DBWSBuilder-generated JAX-WS Provider on JRockit
- Support for Eclipse WTP Dynamic Web Project structure
Known Issues
The following are known issues that have been identified as potentially effecting users of EclipseLink 2.1. For a list of all open bugs and enhancement requests please see the queries at EclipseLink/Bugs
| Summary | Details |
|---|---|
| EclipseLink JPA with OSGi | In order to use EclipseLink 2.1 OSGi, you must use the org.eclipse.persistence.jpa bundle included with this release. This bundle provides support for Gemini, the reference implementation for the OSGI Java EE integration specifica |
| RCP Development with MOXy | There is a known dependency issue when building RCP applications using the org.eclipse.persistence.moxy bundle in combination with the org.eclipse.core.runtime. For more information and workarounds for this issue, please refer to bug 298318.
|
Resolved Issues
In addition to the features highlighted in the New and Noteworthy section this release also includes a substantial number of bug fixes and enhancement requests.
Property Name Generation from Introspector.decapitalize
The decapitalize method will now leave the property name in uppercase if the first and second characters are uppercase. EclipseLink will use the property name as ID, as detailed in the specification.
Note that this may require a change in some JPQL. For example, if previously you had a method with an annotation such as getCCustomers that would have properties named cCustomers, you will now have Customers.
Retention Policy
The EclipseLink 2.1 (Helios) release will remain available for download from the primary download page until the next release is shipped. At that point it will be moved to the previous releases where it remain for a minimum period of 2 years before becoming available for archival.
Future Releases
For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the project summary.