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"
m (→MOXy) |
m (→MOXy) |
||
| Line 45: | Line 45: | ||
** Bootstrap from XSD (produces dynamic entities based on JAXB schema to class generation) or XML config | ** Bootstrap from XSD (produces dynamic entities based on JAXB schema to class generation) or XML config | ||
** Customize bindings using eclipselink-oxm.xml | ** Customize bindings using eclipselink-oxm.xml | ||
| + | ** Access dynamic entities using property names or XPath statements | ||
=== SDO === | === SDO === | ||
Revision as of 14:18, 15 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
New and Noteworthy
JPA
- Advanced Querying
- Casting in JPQL with TREAT...AS and in Criteria
- Batch IN and EXISTS reading modes for queries and mappings
- FUNC in and JPQL to invoke database functions
- Support Functions in JPQL: ORDER BY, GROUP BY, HAVING, constructors, like - bug 306766, bug 295363
- Support for referencing manually defined Query Keys in JPQL - bug 311757
- Optimized inheritance querying - bug 310505
- 1:M join fetching with pagination, cursors
- AttributeGroup support for Fetch, Load, Copy & Merge of partial entities
- batch writing with multiple tables/inheritance
- eclipselink-orm.xml: Additional support for advanced mapping configuration - (bugs)
- Platform Support
- New Server Platform - SAPNetWeaver_7_1_Platform configured using TargetServer.SAPNetWeaver_7_1
- New Database Platform - SymfowarePlatform
- OSGi JPA: Future compatibility for OSGi Enterprise specification for JPA as implemented in Gemini JPA Project.
- Moved previous functionality into org.eclipse.persistence.jpa.osgi fragment which extends org.eclipse.persistence.jpa bundle
MOXy
- JAXB 2.2 Compliance
- Advanced Configuration using eclipselink-oxm.xml to externalize JAXB and extended mappings
- Mapping Enhancements
- Added support for multi-dimensional arrays
- Added support for untyped key based mapping (where the property is type Object)
- JAXB schema generation supports EclipseLink extensions
- Dynamic Persistence
- Bootstrap from XSD (produces dynamic entities based on JAXB schema to class generation) or XML config
- Customize bindings using eclipselink-oxm.xml
- Access dynamic entities using property names or XPath statements
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
Examples
- TBD
Other Projects
Within the Helios release there are other projects that either include EclipseLink or offer complementary functionality.
- Eclipse WTP Dali 3.2.0
- EclipseRT Jetty StarterKit Tutorial with EclipseLink
- Swordfish 0.10 - uses EclipseLink SDO
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 |
|---|---|
| ElementCollection of Embeddable does not support AttribuiteChangeTracking | When using an element collecion of embeddables the underlying AggregateCollectionMapping does not support attribute change tracking. This will effect the use of AttributeGroup (CopyGroup and serialized FetchGroup). |
| 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.
Deprecated Functionality
In EclipseLink 2.1 the following features/API have been deprecated. Please upgrade to the suggested alternatives to avoid issues in the future when these deprecated features/AIP might be removed.
| Summary | Details |
|---|---|
| ObjectCopyPolicy | The ObjectCopyPolicy has been replaced with the CopyGroup. The full API from ObjectCopyPolicy is supported by CopyGroup requiring only a minor class name change in user code. |
| ObjectLevelReadQuery.addPartialAttribute | Partial attribute queries have been deprecated and replaced with the use of FetchGroup |
| ReadObjectQuery.selectionKey (Vector) | Replaced with the use of an object for single part keys and a CacheId for composite keys. The replacement API is: ReadObjectQuery#selectionId. |
| BasicMap, BasicCollection, CollectionTable | Deprecated in 2.0, these native mappings and supported configuration annotations are now supported by JPA 2.0's ElementCollection mapping and supported configuration annotations and orm.xml. |
Removed Functionality
TODO: Was any previously deprecated functionality removed or any functionality that could not be deprecated first removed?
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.