4 Replies Latest reply on May 26, 2006 5:37 PM by asack

    .war classpath issue in 4.0.3SP1

    just_a_w

      I have a .war file that works fine in 4.0.2. But when I run it in 4.0.3SP1, I get an exception: java.lang.NoClassDefFoundError: org/dom4j/xpath/DefaultXPath

      The dom4j-full.jar is in WEB-INF/lib (and it contains org.dom4j.xpath.DefaultXPath). And it works fine in 4.0.2.

      Any idea what might be wrong?

      Thanks

        • 1. Re: .war classpath issue in 4.0.3SP1
          gbrits

          I've got the exact same problem.

          Did you solve your problem in the mean time? anf if so, how?

          Thanks

          • 2. Re: .war classpath issue in 4.0.3SP1
            sadiq

            I had the same problem. SOmehow, I managed to solve it. It's a JBoss issue, concerning de XPath class from dom4j. In jboss >= 4.0.3 there is a custom package of dom4j, which should be replaced by the version which has the XPath class. I have copied the dom4j-1.6.1 and the jaxen jars into the lib folder of jboss and it worked just fine. Strangely enough, I had to copy the 2 jars as dom4j.jar and jaxen.jar (the dom4j-1.6.1.jar name did not work). After that, I kept on aop-ing.

            • 3. Re: .war classpath issue in 4.0.3SP1
              prideafrica

              I just did the same thing - copying dom4j-1.6.1.jar and jaxen-all.jar to JBoss-4.0.3SP1 /lib, but it did not work. Has anyone else been able to resolve this issue successfully?

              • 4. Re: .war classpath issue in 4.0.3SP1
                asack

                Works for me (I add dom4j and jaxen in /lib and now I have XPATH). Is this in just a WAR or a WAR within an EAR? Regardless, JBoss should check your dom4j in WEB-INF/lib before loading the cached boostrap one in the UCL.