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"
(→Known Issues) |
(→Eclipse PDE and MOXy) |
||
| Line 54: | Line 54: | ||
In order to use EclipseLink 2.1 OSGi, you ''must'' use the '''org.eclipse.persistence.jpa''' included with this release. This bundle provides support for Gemini, the reference implementation for the OSGI Java EE integration specification. | In order to use EclipseLink 2.1 OSGi, you ''must'' use the '''org.eclipse.persistence.jpa''' included with this release. This bundle provides support for Gemini, the reference implementation for the OSGI Java EE integration specification. | ||
| − | === | + | === RCP Development with MOXy === |
| − | + | There is a known issue that is exposed when the MOXy bundle is included in combination with <code>org.eclipse.core.runtime</code> in an application's list of dependent bundles. When the app is loaded in a Galileo | |
| − | in | + | build of the Eclipse IDE, erroneous red-X's will appear with the message: <tt>Unsatisfied Version Constraint: 'org.eclipse.core.runtime: |
| − | the message: <tt>Unsatisfied Version Constraint: 'org.eclipse.core.runtime: 0.0.0'</tt>. When the app is loaded in a Helios build, the red-X's do not appear but at ''runtime'' the app will not initialize and the error console will report the same <tt>Unsatisfied Version Constraint</tt> | + | 0.0.0'</tt>. When the app is loaded in a Helios build, the red-X's do not appear but at ''runtime'' the app will not initialize and the error console will report the same <tt>Unsatisfied Version Constraint</tt> message. |
| − | + | For more information and workarounds for this issues, please refer to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=298318 bug 298318]. | |
| − | + | ||
| − | + | ||
| − | + | ||
== Resolved Issues == | == Resolved Issues == | ||
Revision as of 10:16, 4 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
- DBWS
- Support DBWSBuilder-generated JAX-WS Provider on JRockit
- Support for Eclipse WTP Dynamic Web Project structure
Known Issues
OSGi and JPA
In order to use EclipseLink 2.1 OSGi, you must use the org.eclipse.persistence.jpa included with this release. This bundle provides support for Gemini, the reference implementation for the OSGI Java EE integration specification.
RCP Development with MOXy
There is a known issue that is exposed when the MOXy bundle is included in combination with org.eclipse.core.runtime in an application's list of dependent bundles. When the app is loaded in a Galileo
build of the Eclipse IDE, erroneous red-X's will appear with the message: Unsatisfied Version Constraint: 'org.eclipse.core.runtime:
0.0.0'. When the app is loaded in a Helios build, the red-X's do not appear but at runtime the app will not initialize and the error console will report the same Unsatisfied Version Constraint message.
For more information and workarounds for this issues, 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.