Known Issues

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

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.