Known problems and limitations for EJB applications
Known problems can apply when you are working with WebSphere® Developer Tools. For example, you can receive errors when you import a Java archive (JAR) file that you create by using EJB 2.1 or earlier.
For more information about limitations and troubleshooting tips, see Known problems and limitations for WebSphere Application Server Developer Tools for Eclipse.
Errors when you import JAR files that you create by using EJB 2.1 or earlier
You can receive errors when you import JAR files that you create by using EJB 2.1 or earlier. Some or all of the classes in the deployment code can cause compiler errors. These classes are not needed for deploying or running your EJB application.
You can work around this problem. Delete the following files:
- All of the files in the following Java packages:
- com.ibm.ejs.container
- com.ibm.websphere.csi
- package.websphere_deploy
- package.websphere_deploy.backend ID
- org.omg.stub.java.lang
- org.omg.stub.javax.ejb
- The RdbRuntimeUpdateTemplate.java file from the com.ibm.ws.ejbdeploy.JProject Name.backend ID class.
- The following files from the package that contains the bean code:
- _EJS*_*_Tie.java
- _EJS*_*_Stub.java
- _*_Stub.java
- Concrete_*.java
- EJSCMP*_*.java
- EJSLocalCMP*_*.java
- EJSRemoteCMP*_*.java
Limitation when you import an EJB JAR file that does not have a deployment descriptor
If you attempt to import a EJB jar file using the option ejb-jar.xml, and you select a Liberty server configured with a JRE version 6 or earlier as the target runtime, the OK button is not enabled, and no error is displayed in the wizard.
, and the EJB jar file you select does not have a deployment descriptor,