Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Release/2.0.2
EclipseLink 2.0.2 Patchset
The EclipseLink 2.0.2 patch set: April 21st 2010
EclipseLink 2.0.2 is a patch set on the 2.0 stream. Please see link below for a full list of bugs that have been fixed in 2.0.2.
ContentsDownload EclipseLink 2.0.2 |
Resolved Issues
The following table lists of few of the issues resolved in 2.0.2. For a complete list, please see the link below the table.
Component | Issue | Description |
---|---|---|
JPA | ||
Utils - Workbench | U | |
JPA | ||
JPA | ||
MOXy |
Resolved Bug Queries
- All Bugs and Enhancements Requests (ordered by priority)
- By Component: JPA, MOXy, SDO, DBWS, Foundation
Known Issues
All known issues with EclipseLink are tracked in the Eclipse bugzilla database. Queries for current open bugs in EclipseLink are available here.
EclipseLink DBWS with JRockit JVM
EclipseLink DBWS deployment may fail in JRockit VM environment. When generating a WAR file for deployment, the EclipseLink Database Web Services (DBWS) design-time utility uses a version of ASM for code generation which is not compatible with later versions of JRockit. This results in a deployment failure with the SOAP message exception Illegal target of jump or branch.
Note: This issue does not occur when running the application server in a Sun JVM environment.
To generate a DBWS deployment WAR file that will successfully deploy in a JRockit JVM environment, use this procedure:
Note: You can complete this procedure using an IDE, such as Eclipse or Oracle JDeveloper.
- Create a new project. Add the following libraries to the classpath:
- Java EE
- JAX-WS 2.0 Library
- jlib/eclipselink.jar
- JDBC Library
- utils/dbws/eclipselink-dbwsutils.jar
- utils/dbws/javax.wsdl_1.6.2.v200806030405.jar
- Import the dbws-bulider.xml file and add it to the project classpath.
- Create a new file named META-INF/services/org.eclipse.persistence.tools.dbws.DBWSPackager in the project's src directory. The file should contain the following, single line:
org.eclipse.persistence.tools.dbws.JDevPackager
Add this newly created file to the project classpath. - Use the DBWSBuilder utility to generate the web service artifacts in the specified directory:
- Main class: org.eclipse.persistence.tools.dbws.DBWSBuilder
- Arguments: -builderFile dbws-builder.xml -stageDir . -packageAs jdev
- Rebuild the project. This will generate a DBWSProvider.class file.
- Use the web service artifacts to generate a WAR deployment profile. The .war file should contain the following:
- WEB-INF/web.xml
- WEB-INF/classes/_dbws/DBWSProvider.class
- WEB-INF/classes/META-INF/eclipselink-dbws.xml
- WEB-INF/classes/META-INF/eclipselink-dbws-or.xml
- WEB-INF/classes/META-INF/eclipselink-dbws-ox.xml
- WEB-INF/classes/META-INF/eclipselink-dbws-sessions.xml
- WEB-INF/wsdl/eclipselink-dbws.wsd
- WEB-INF/wsdl/eclipselink-dbws-schema.xsd
- You can now deploy the WAR file to your application server.
Bean Validation not being triggered
Due to Issue 311225 Bean Validation is not being triggered. Here are possible workarounds.
- Add add an entity listener to the Entity being validated.
- Manually cause the flag within the DescriptorEventManager for the validated descriptor to be set on. This can be done by adding a 'dummy' Listener then removing it as follows
DescriptorEventAdapter dummyListener = new DescriptorEventAdapter(); DescriptorEventManager eventManager = em.unwrap(Session.class).getDescriptor(Employee.class).getDescriptorEventManager(); eventManager.addListener(dummyListener); eventManager.removeListener(dummyListener);
Certified Configurations
Persistence Specifications Supported
Specification | Version | Notes |
---|---|---|
EJB 3.0 (Java Persistence) - JSR 220 | 1.0 | |
Java Persistence (JPA) - JSR 317 | 2.0 | Reference Implementation |
Service Data Objects SDO - JSR 235 | 2.1.1 | Reference Implementation provided by EclipseLink 1.1.0.r3634 |
Java XML Binding Architecture (JAXB) - JSR 222 | 2.1 |
Java Persistence (JPA) 1.0 & 2.0
EclipseLink 2.0.1 provides both JPA 2.0 and 1.0 functionality. In order to remain backwards compatible with JPA 1.0 some limitations have been imposed. The following table illustrates the usage of each version of JPA with the available library versions.
Java Architecture | JPA 2.0 javax_persistence_2.0.0 Included with EclipseLink ZIP |
JPA 1.0 javax_persistence_1.0.0 Included with EclipseLink ZIP |
JPA 1.0 javax_persistence_1.0.0 Orbit (signed) |
---|---|---|---|
Java SE eclipselink.jar |
|||
Java SE bundles |
|||
Java EE eclipselink.jar |
|||
Java EE bundles |
|||
OSGi (Equinox) bundles |
Database Platform Certifications
- Database Platform Certification Notes
- (O) - Certified by Oracle TopLink QA for the EclipseLink project