Jump to: navigation, search

Difference between revisions of "EclipseLink/Release/2.1.3"

(EclipseLink 2.1.3 Release Notes)
(Future Releases)
 
(One intermediate revision by the same user not shown)
Line 71: Line 71:
  
 
For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the [http://www.eclipse.org/projects/project_summary.php?projectid=rt.eclipselink project summary].
 
For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the [http://www.eclipse.org/projects/project_summary.php?projectid=rt.eclipselink project summary].
 +
 +
[[Category:EclipseLink|Release/2.1.3]]

Latest revision as of 14:43, 24 October 2011

HeliosEclipseLink

EclipseLink 2.1.3 Release Notes

The EclipseLink 2.1.3 patchset focuses on providing bug fixes on the 2.1.0 stream.

New and Noteworthy

Helios Projects leveraging EclipseLink

Within the Helios release there are other projects that either include EclipseLink or offer complementary functionality.

Standards Based

  • JPA 2.0
  • JAXB 2.2
  • SDO 2.1.1

Known Issues

The following are known issues that have been identified as potentially effecting users of EclipseLink 2.1.3. For a list of all open bugs and enhancement requests please see the queries at EclipseLink/Bugs

The following bug queries can be used by find known issues with specific feature areas. They return bugs reported against 2.1.3


Result class of getSingleresult differs from earlier releases

In EclipseLink 2.1.1, the getSingleResult of a scalar native query may return return different classes than in EclipseLink 1.x. This will require a modification to your code.

For example, this code:

        Query q = em.createNativeQuery("SELECT 1,2 FROM dual ");
        Object obj = q.getSingleResult();

will return:

  • EclipseLink 1.x: A List with as first element a BigDecimal
  • EclipseLink 2.x: An Array with as first element a BigDecimal.

Reference 3394987

Resolved Issues

In addition to the features highlighted in the New and Noteworthy section this release also includes a substantial number of bug fixes and enhancement requests.

Property Name Generation from Introspector.decapitalize

The decapitalize method will now leave the property name in uppercase if the first and second characters are uppercase. EclipseLink will use the property name as ID, as detailed in the specification.

Note that this may require a change in some JPQL. For example, if previously you had a method with an annotation such as getCCustomers that would previously have had a property named cCustomers, you will now need to use property CCustomers.

Future Releases

For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the project summary.