Difference between revisions of "EclipseLink/Release/2.2.0"
|Line 36:||Line 36:|
=== DBWS ===
=== DBWS ===
=== Standards Based ===
=== Standards Based ===
Revision as of 13:30, 16 February 2011
EclipseLink 2.2.0 Release Notes
The EclipseLink 2.2 release focuses on providing advanced persistence features for user of relational, XML and Web Services to expose extended persistence features that naturally extend the industry standards in these spaces. As well as these new features, a great emphasis was placed on bug fixing in this release.
New and Noteworthy
- Monitor persistence performance with the new Performance Monitor. ...learn more
- Indexes can now be generated on the Database using our Index generation feature. ...learn more
- Allow for auto appending of strings to CREATE TABLE statements. ...learn more
- Allow Delete Cascading to be handled by the database, using CascadeOnDelete. ...learn more
- Filter data using our new AdditionalCriteria. ...learn more
- Partition row data across tables using our new PartitioningPolicy. ...learn more
- EclipseLink support for JPA in OSGi is deprecated in this release and will be replaced by the OSGi Enterprise Spec compliant Gemini JPA project in a future release. OSGi developers are encouraged to migrate to Gemini JPA with EclipseLink 2.2.
- MOXy external metadata and annotation support
- MOXy annotation support equivalent to our XML metadata support
- Support to allow configuration similar to that of deployment XML
- Support for MOXy Equivalents of relevant JPA Annotations
- Dynamic MOXy - Bootstrapping from EclipseLink Externalized Metadata....learn more
- Using EclipseLink JAXB with the Spring Framework....learn more
- Use EclipseLink JPA & JAXB to create a RESTful web service....learn more
- Build a DBWS service by retrieving Custom SQL result-set metadata at design time....learn more
- DBWS Update operation now supporting Sparse Merges
- Run a DBWS service in an OSGi environment....learn more
- JPA 2.0
- JAXB 2.2
- SDO 2.1.1
The following are known issues that have been identified as potentially effecting users of EclipseLink 2.2. For a list of all open bugs and enhancement requests please see the queries at EclipseLink/Bugs
- 263944 - Removed an unmapped access element from the transformation element of the eclipselink orm schema. The correct access attribute metadata remains and should be the one that is used. See the bug for more details.
- 331234 - Corrected a JPA specification violation surrounding the xml-mapping-metadata-complete flag. The incorrect behavior however may have been employed by some users meaning they could encounter some issues and need to re-configure their xml metadata. See the bug for more details.
The following bug queries can be used by find known issues with specific feature areas. They return bugs reported against 2.2.
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.
- All Fixed Bugs and enhancement requests
In EclipseLink 2.2 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.
|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.|
The EclipseLink 2.2 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.
For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the project summary.