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.
Difference between revisions of "EclipseLink/Release/1.1"
| Line 1: | Line 1: | ||
<div></div> | <div></div> | ||
| − | = EclipseLink 1.1 Release | + | = EclipseLink 1.1 Release Notes = |
<table><tr> | <table><tr> | ||
<td width="75%" valign="top"> | <td width="75%" valign="top"> | ||
| Line 7: | Line 7: | ||
== Release Status == | == Release Status == | ||
| − | The release currently scheduled for | + | The release currently scheduled for March 11th. |
== Feature Overview == | == Feature Overview == | ||
| − | * JPA 2. | + | * JPA Enhancements |
| − | * | + | * SDO 2.1.1 and Data Access Service |
| − | + | * First release of DBWS | |
</td> | </td> | ||
| Line 22: | Line 22: | ||
</table> | </table> | ||
| − | === JPA 2.0 | + | === JPA 2.0 Enhancements === |
| − | EclipseLink | + | 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 == | == Download == | ||
Revision as of 17:04, 5 March 2009
EclipseLink 1.1 Release Notes
Release StatusThe release currently scheduled for March 11th. Feature Overview
|
JPA 2.0 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
Currently the 1.1 release is producing nightly and milestone builds 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 |
|---|
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 |
|---|