Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Release/1.1"

(Known Issues)
(Known Issues)
Line 73: Line 73:
 
! Core
 
! Core
 
! Remove JPA dependency from 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.   
+
! <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>
  
 
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).
 
|-
 
|-
 
|}
 
|}

Revision as of 11:27, 17 March 2009

EclipseLink 1.1 Release Notes

Release Status

The release currently scheduled for March 11th.

Feature Overview

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

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.

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

Download

The 1.1.0 release is available for download.

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

All Bugs Resolved in 1.1.0

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

Copyright © Eclipse Foundation, Inc. All Rights Reserved.