Difference between revisions of "EclipseLink/Release/1.1"
|Line 101:||Line 101:|
253934MOXy Default Namespace, Root Element, & Inheritance Problem
Revision as of 11:59, 19 March 2009
EclipseLink 1.1 Release Notes
The release currently scheduled for March 11th.
The EclipseLink team continues to enhance the JPA support with development of the JPA 2.0 (JSR 317) Reference Implementation as the primary target. While the majority of the new features for JPA 2.0 are planned for the EclipseLink 2.0 release some new capabilities have been added to this release.
- Undirectional 1:M Mapping: You can now have a 1:M mapping without requiring the M:1 mapping pointing back from target entity nor do you require a separate join table to hold the associations.
- TABLE_PER_CLASS Inheritance has been added giving greater flexibility in how your relational tables associate with the classes in a hierarchy.
SDO 2.1.1 and Data Access Service
This release of EclipseLink includes an implementation of SDO 2.1.1 (JSR 235). This implementation conforms to the final draft and is being included with the final draft as the reference implementation.
SDO developers wishing to leverage existing POJO models, including JPA entities, can use the included Data Access support to wrap either static or dynamic data objects leveraging MOXy mappings (JAXB annotations or native XML metadata).
First release of DBWS
The first release of EclipseLink DBWS allows developers to easily and efficiently expose database constructs (tables, SQL, stored procedures).
The 1.1.0 release is available for download.
All known issues with EclipseLink are tracked in the Eclipse bugzilla database. Queries into this database for EclipseLink, including all bugs fixed in 1.1, are available here. The following is a partial list of key bugs addressed in the 1.1 release.
|220394||Core||improve insert performance|| Improvements to the performance of inserts. Main change is that now new objects do not build change records (still create
change set, but it is empty).
|244241||Core||connection not released on query timeout when cursor used|| If the query's timeout was set sufficiently low enough that it returned before
the cursor can be returned (i.e. query.setQueryTimeout() is set to be 1 second), the database connection used was not returned to the pool after the query was executed.
|252705||JPA||Potential to lose @PrePersist changes when using EntityManager.merge|
|253701||JPA||Classloader leak in JavaSECMPInitializer|| After undeploy of an application, EclipseLink still had a reference to web app's
ContextClassLoader, preventing proper undeployment of the web app.
|256277||JPA||Endless loop on @PrePersist resulting in a flush() call.||Before the fix, A loop could occur if a PrePersist resulting from a flush() caused another flush().|
|259993||JPA||em.find() hangs up in some situations on WebSphere 220.127.116.11||Some application servers call em.close() between beforeCompletion() and afterCompletion(). This caused EclipseLink to be in an incorrect state during merge.|
|259493||MOXy||Thread Safety Issue - XML Context and Object Ref Mapping|
|MOXy | Default Namespace, Root Element, & Inheritance Problem|
|255416||MOXy||XmlChoiceCollectionMapping's field-to-class-associations were not always read correctly|
|255832||MOXy||Date conversions failed in a multithreaded environment|
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 that may effect users of EclipseLink 1.1.
|268769||Core||Remove JPA dependency from core|| EclipseLink jar from 1.1 requires a dependency on the JPA jar. This dependency has been removed from the 1.1.1 stream.
Impact: Importing or otherwise using EclipseLink Query framework (specifically ObjectLevelReadQuery) will require that javax.persistence_1.0.0.jar be on the classpath. The main impact will be on DBWS and EclipseLink ORM Native API users (ie. Non-Jpa).
The impact on DBWS is that the JPA jar must be included on the classpath when invoking the DBWSBuilder utility.