-
1. Re: JBoss 3.2.3, Tomcat 4.1.29 NoClassDefFoundError
starksm64 Mar 15, 2004 8:16 PM (in response to jboss.thejavateam.com)There is a conflict with the version of jdom you compiled against that the jdom.jar found in jboss-3.2.3/lib/jdom.jar. Try replacing this with your version of jdom, or add a jboss-web.xml to your war to override the
jboss version of the classes.
<jboss-web>
<class-loading java2ClassLoadingCompliance="false">
<loader-repository>
mydomain:war=mywar.war
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</class-loading>
</jboss-web> -
2. Re: JBoss 3.2.3, Tomcat 4.1.29 NoClassDefFoundError
jrinderle Apr 14, 2004 5:13 PM (in response to jboss.thejavateam.com)I had the same problem, but found an easy fix! If you repackage the JDOM jar to include the saxpath and jaxen classes, it will work.
Create a temp. folder. Extract jdom.jar, saxpath.jar, jaxen-core.jar, and jaxen-jdom.jar into that folder. Now create a new jdom.jar file which contains all of the class files you just extracted. (You can exclude the META-INF folder). Replace the jdom.jar in the JBoss lib folder with the new JAR you just created. Restart JBoss and give it a try. -
3. Re: JBoss 3.2.3, Tomcat 4.1.29 NoClassDefFoundError
sjwoodman Oct 10, 2005 10:40 AM (in response to jboss.thejavateam.com)"jrinderle" wrote:
Create a temp. folder. Extract jdom.jar, saxpath.jar, jaxen-core.jar, and jaxen-jdom.jar into that folder. Now create a new jdom.jar file which contains all of the class files you just extracted. (You can exclude the META-INF folder). Replace the jdom.jar in the JBoss lib folder with the new JAR you just created. Restart JBoss and give it a try.
This worked for me too on JBoss 3.2.3 using jdom-1.0. I packaged jaxen-core, jaxen-jdom, saxpath and jdom into one new jdom.jar. Then just copy it to /lib and overwrite the original.
Thanks!