[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=RT&product=EclipseLink&target_milestone=1.1&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Bugs Resolved in 1.1.0]

== Known Issues ==

== Known Issues ==

Line 67:

Line 123:

! Summary

! Summary

! Comments

! Comments

+

|-

+

| 268769

+

| Core

+

| Remove JPA dependency from core

+

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

+

+

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/>

Contents

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

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.

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