Difference between revisions of "EclipseLink/Release/1.0.1"

From Eclipsepedia

Jump to: navigation, search
(Known Issues)
(Known Issues)
Line 79: Line 79:
 
|-
 
|-
 
|}
 
|}
 +
 +
[[Category:EclipseLink]]

Revision as of 08:38, 18 October 2011

Release Notes

The 1.0.1 release is a patch for EclipseLink 1.0. Please see the release notes for EclipseLink 1.0 for more information on EclipseLink 1.0.

Download

The 1.0.1 release is available for download here. The release offers both a zip file intended for standard JavaSE and JavaEE usage. There is also a ZIP file provided of OSGi bundles.

Resolved Issues

All known issues with EclipseLink are tracked in the Eclipse bugzilla database. Queries into this database for EclipseLink, including all bugs fixed in 1.0.1, are available here. The following is a partial list of some bugs fixed in 1.0.1.

Bug Component Summary Comments
237545 JPA Attribute change tracking did not properly work on 1:M with @OrderBy
241979 JPA MappedSuperclasses were not weaved unless they contained a OneToOneMapping
236726 JPA blank as a password was not accepted
240166 SDO sdo-compiler failed on OASIS xsd files
241308 JPA Primary key was incorrectly assigned to embeddable class field with the same name as the primary key field's name
241388 JPA JPA cache was not always valid after a certain series of EntityManager operations
243943 JPA Regression: checkCacheForObject via UnitOfWork if object only in Session and shouldCheckCacheOnly

Known Issues

All known issues with EclipseLink are tracked in the Eclipse bugzilla database. Queries for current open bugs in EclipseLink are available here. The following is a partial list of some bugs bugs that are still open in 1.0.1.

Bug Component Summary Comments
239882 Utils - Package Renamer The Package Renamer utility does not always properly rename xml files Workaround: Use your existing TopLink 10.1.3X xml files
246762 Utils - Workbench The Workbench Session Configuration editor does not provide a way to set useExternalConnectionPooling and externalTransactionController options on the ReadConnectionPool and SequenceConnectionPool. Workaround: Manually edit sessions.xml to add the appropriate xml tags: <external-connection-pooling>true/false<external-connection-pooling> and <external-transaction-controller>true/false</external-transaction-controller>