The 1.0.2 release is an incremental patch for EclipseLink 1.0.1. Please see the release notes for EclipseLink 1.0.1 for more information on the previous release of EclipseLink.
The 1.0.2 release is available for download here. The release offers both a zip file intended for standard JavaSE and JavaEE usage. There is also a ZIP file provided of OSGi bundles.
All known issues with EclipseLink are tracked in the Eclipse bugzilla database. Queries into this database for EclipseLink, including all bugs fixed in 1.0.2, are available here. The following is a partial list of some bugs fixed in 1.0.2.
|247070||JPA||testBUG241388 in org.eclipse.persistence.testing.tests.jpa.fieldaccess.advanced.AdvancedJunitTest failed on MySQL|
|248295||JPA||Support for running the JPA tests on GlassFish|
|245548||JPA||17 tests in EntityManagerJUnitTestSuite failed on WebSphere|
|245130||Mapping Workbench||ClassCastException after changing the L&F on Linux|
|249664||JPA||application jar files locked on Windows for application with *orm.xml file|
|241851||Doc||javadocs show cache-size default as 1000 instead of 100|
|249121||Test||Need to add Oracle JDBC Specific tests for running on Server|
|250970||Foundation||EclipseLink incompatible with Oracle JDBC Driver 22.214.171.124|
|247735||JPA||Reading persistence XML fails with some XML parsers due to unsupported SAX property.|
|244871||Foundation||PERF: Optimize primitive jdbc isNull call for non 0 values|
|246317||JPA||Can't connect to two different databases in Java SE environment using two persistence.xml files|
|249339||MOXy||JAXBContextFactory Shouldn't attempt to generate using a JAXB 1.0 Object Factory|
|247068||MOXy||moxy tries to automap static vars, does not work with JPA|
|249338||JPA||Relation removes to detached objects are lost when merging|
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 in 1.0.2.
|239882||Utils - Package Renamer||The Package Renamer utility does not always properly rename xml files||Workaround: Use your existing TopLink 10.1.3X xml files|