This document applies only to the following language version(s):
Enterprise Java™Beans Deploy run from a IBM WebSphere Application Server environment may report NoClassDefFoundErrors.
Classpath information is missing from the MANIFEST.MF Class-Path attribute.
Resolving the problem
This error will occur if there are missing classpath entries that are needed by EJBDeploy. These classpath entries should be added to the MANIFEST.MF Class-Path so that EJBDeploy can set the classpath of the EJB project before deploying it.
If the class file being referenced should exist with the application (i.e. in the EAR file) then its corresponding JAR file should be referenced in the MANIFEST.MF Class-Path attribute. For instance, If there were any JAR files that were added to the Java Build Path of the EJB module they should be added to the Class-Path attribute of the MANIFEST.MF. However, if the class file being referenced does not need to exist within the application, then it is possible to specify the location of the jar files containing the class by using the -cp command line option for EJBDeploy.
|Application Servers||Runtimes for Java Technology||Java SDK|