ClassDefNotFound when deploying MDB in EAR

[laverite]

I am trying to deploy an EAR to jboss3.2.2RC4 which includes my MDB in a jar. The MDB jar has a Manifest with Class-Path set for all necessary jars.

However when I try and deploy my EAR I get the following exception:

2004-06-18 17:29:23,065 WARN [org.jboss.ejb.EJBDeployer] Verify failed; continuing
java.lang.NoClassDefFoundError: org/jaxen/JaxenException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1590)
at java.lang.Class.getConstructor0(Class.java:1762).....

But this class is in fact in one of tha jars within the EAR (jaxen-full.jar). I've even tried to remove jaxen-full.jar from the EAR to verify the MANIFEST entry is honored during deployment and jboss oes complains that it was unable to located the file indicated in the MANIFEST.

I've also tried placing jaxen-full.jar in common lib directory. I've restarted JBOSS as well and repackaged and redeployed numerous of times while thinking this might be a class-loading issue. I can't seem to get around it. Any insight ts would be greatly appreciated. Thanks.

[stephanenicoll]

Have you tried to put in the server's lib directory?

$JBOSS_HOME/server/default/lib if you're using the default server.

You can also declare your lib with a java module inside application.xml


jaxen-full.jar


Regards,

Stephane

[laverite]

Yes, jaxen-full.jar in in the:

$JBOSS_HOME/server/default/lib

directory.....still no luck, any other suggestions?

[genman]

If you deploy the .jar file in the lib directory and still don't have luck, then I bet either the .jar is corrupted (which can happen if it's been in CVS or FTPd), permissions issue, or you're not running the default deployment.

Try to run a test program using the .jar file in the lib directory. Also, when you are assembling the .jar file with the EJB, use this sort of ANT jar command:








the .jar would contain lib/comm.jar, for example...

[laverite]

I found the answer at the post below. I was missing saxpath.jar from the classpath and this resulted in the error. Thanks to all for taking the time to look into this.

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49582