Difference between revisions of "EclipseLink/Release/1.1"

From Eclipsepedia

Jump to: navigation, search
(Resolved Issues)
 
(11 intermediate revisions by 3 users not shown)
Line 5: Line 5:
 
<td width="75%" valign="top">
 
<td width="75%" valign="top">
  
== Release Status ==
+
The EclipseLink 1.1.0 release shipped March 11th, 2009. Additional patch-sets of this release are available:
 +
* [[EclipseLink/Release/1.1.1 | EclipseLink 1.1.1 Patch-set]] - May 15th, 2009
 +
* [[EclipseLink/Release/1.1.2 | EclipseLink 1.1.2 Patch-set]] - Release Candidate (Galileo Target)
  
The release currently scheduled for March 11th.
+
== Download ==
 +
 
 +
The 1.1.0 release is available for [http://www.eclipse.org/eclipselink/downloads/index.php#1.1.0 download].
  
 
== Feature Overview ==
 
== Feature Overview ==
Line 40: Line 44:
 
The first release of EclipseLink DBWS allows developers to easily and efficiently expose database constructs (tables, SQL, stored procedures).
 
The first release of EclipseLink DBWS allows developers to easily and efficiently expose database constructs (tables, SQL, stored procedures).
  
== Download ==
 
 
The 1.1.0 release is available for [http://www.eclipse.org/eclipselink/downloads/index.php#1.1.0 download].
 
  
 
== Resolved Issues ==
 
== Resolved Issues ==
Line 55: Line 56:
 
! Comments
 
! Comments
 
|-
 
|-
! 220394  
+
| {{bug|220394}}
! Core
+
| Core
! improve insert performance   
+
| improve insert performance   
! Improvements to the performance of inserts.  Main change is that now new objects do not build change records (still create
+
| 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).
change set, but it is empty).
+
 
|-  
 
|-  
 
+
| {{bug|244241}}  
! 244241   
+
| Core
! Core
+
| connection not released on query timeout when cursor used   
! connection not released on query timeout when cursor used   
+
| If the query's timeout was set sufficiently low enough that it returned before
! 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
 
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
 
second), the database connection used was not returned to the pool after the
 
query was executed.
 
query was executed.
 
|-
 
|-
 
+
| {{bug|252705}}
! 252705
+
| JPA
! JPA
+
| Potential to lose @PrePersist changes when using EntityManager.merge
! Potential to lose @PrePersist changes when using EntityManager.merge
+
|
!
+
 
|-
 
|-
 
+
| {{bug|253701}}
! 253701
+
| JPA  
! JPA  
+
| Classloader leak in JavaSECMPInitializer   
! 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.
! After undeploy of an application, EclipseLink still had a reference to web app's
+
ContextClassLoader, preventing proper undeployment of the web app.
+
 
|-
 
|-
 
+
| {{bug|256277}}
 
+
| JPA
! 256277
+
| Endless loop on @PrePersist resulting in a flush() call.
! JPA
+
| Before the fix, A loop could occur if a PrePersist resulting from a flush() caused another flush().  
! 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().  
+
 
|-
 
|-
 
+
| {{bug|259993}}
! 259993  
+
| JPA
! JPA
+
| em.find() hangs up in some situations on WebSphere 7.0.0.1   
! em.find() hangs up in some situations on WebSphere 7.0.0.1   
+
| Some application servers call em.close() between beforeCompletion() and afterCompletion().  This caused EclipseLink to be in an incorrect state during merge.   
! Some application servers call em.close() between beforeCompletion() and afterCompletion().  This caused EclipseLink to be in an incorrect state during merge.   
+
 
|-
 
|-
! 259493
+
| {{bug|259493}}
! MOXy
+
| MOXy
! Thread Safety Issue - XML Context and Object Ref Mapping   
+
| Thread Safety Issue - XML Context and Object Ref Mapping   
!
+
|
 
|-
 
|-
| {253934@bug} | MOXy | Default Namespace, Root Element, & Inheritance Problem   
+
| {{bug|253934}}  
 +
| MOXy  
 +
| Default Namespace, Root Element, & Inheritance Problem   
 +
|
 
|-
 
|-
! 255416
+
| {{bug|255416}}
! MOXy
+
| MOXy
! XmlChoiceCollectionMapping's field-to-class-associations were not always read correctly   
+
| XmlChoiceCollectionMapping's field-to-class-associations were not always read correctly   
!
+
|
 
|-
 
|-
 
+
| {{bug|255832}}
! 255832
+
| MOXy
! MOXy
+
| Date conversions failed in a multithreaded environment   
! Date conversions failed in a multithreaded environment   
+
|
!
+
 
|-
 
|-
 
 
|}
 
|}
  
Line 130: Line 124:
 
! Comments
 
! Comments
 
|-
 
|-
! 268769
+
| 268769
! Core
+
| Core
! Remove JPA dependency from core
+
| Remove JPA dependency from core
! <b>EclipseLink jar from 1.1 requires a dependency on the JPA jar. This dependency has been removed from the 1.1.1 stream.  </b>
+
| <b>EclipseLink jar from 1.1 requires a dependency on the JPA jar. This dependency has been removed in the 1.1.1 stream.  </b>
  
 
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).
 
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.
 
The impact on DBWS is that the JPA jar must be included on the classpath when invoking the DBWSBuilder utility.
 +
|-
 +
| 269516
 +
| DBWS
 +
| DBWS 1.1 documentation errors
 +
|<b>The EclipseLink User Guide (ELUG) sections on DBWS has errors</b>
 +
mixing up the DBWS service descriptor file with the DBWSBuilder builder file <br/>
 +
naming conventions of DBWS descriptor file schemas and their locations <br/>
 
|-
 
|-
 
|}
 
|}
 +
 +
[[Category:EclipseLink|Release/1.1]]

Latest revision as of 15:41, 24 October 2011

[edit] EclipseLink 1.1 Release Notes

The EclipseLink 1.1.0 release shipped March 11th, 2009. Additional patch-sets of this release are available:

[edit] Download

The 1.1.0 release is available for download.

[edit] Feature Overview

  • JPA Enhancements
  • SDO 2.1.1 and Data Access Service
  • First release of DBWS

Contents

[edit] JPA Enhancements

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.

These include:

  • 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.

[edit] 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).

[edit] First release of DBWS

The first release of EclipseLink DBWS allows developers to easily and efficiently expose database constructs (tables, SQL, stored procedures).


[edit] 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.1, are available here. The following is a partial list of key bugs addressed in the 1.1 release.

Bug Component Summary Comments
bug 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).
bug 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.

bug 252705 JPA Potential to lose @PrePersist changes when using EntityManager.merge
bug 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.
bug 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().
bug 259993 JPA em.find() hangs up in some situations on WebSphere 7.0.0.1 Some application servers call em.close() between beforeCompletion() and afterCompletion(). This caused EclipseLink to be in an incorrect state during merge.
bug 259493 MOXy Thread Safety Issue - XML Context and Object Ref Mapping
bug 253934 MOXy Default Namespace, Root Element, & Inheritance Problem
bug 255416 MOXy XmlChoiceCollectionMapping's field-to-class-associations were not always read correctly
bug 255832 MOXy Date conversions failed in a multithreaded environment

All Bugs Resolved in 1.1.0

[edit] 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 that may effect users of EclipseLink 1.1.

Bug Component Summary Comments
268769 Core Remove JPA dependency from core EclipseLink jar from 1.1 requires a dependency on the JPA jar. This dependency has been removed in 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.

269516 DBWS DBWS 1.1 documentation errors The EclipseLink User Guide (ELUG) sections on DBWS has errors

mixing up the DBWS service descriptor file with the DBWSBuilder builder file
naming conventions of DBWS descriptor file schemas and their locations