1 Reply Latest reply on May 26, 2005 5:46 PM by Peter Johnson

    Jboss 4.0.2 and Tomcat

    Ram Sarma Newbie


      I wanted to upgrade to Jboss 4.0.2 from Jboss 3.2.3. I have an external
      tomcat (4.x). I've configured to start tomcat through Eclipse. With the
      Eclipse configuration I include <jboss-3.2.3/client/jbossall-client.jar> to the end of my classpath. EVERYTHING WORKS PERFECTLY. I upgrade to 4.0.2, change the classpath entry to <jboss-4.0.2/client/jbossall-client.jar> and try to start tomcat.... FAILS with a NoClassDefFoundError for org/dom4j/Element.

      Just to know if jboss-4.0.2 is configured correctly - i can go to the jmx-console and see all my mbeans as well as my jndi tree. I change the client
      jar in the tomcat classpath to jboss-3.2.3 and everything is fine when tomcat starts up. (ofcourse this will not work because of version mismatches)

      Is there something whacky about the 4.0.2 client jars?


        • 1. Re: Jboss 4.0.2 and Tomcat
          Peter Johnson Master

          A few thoughts on this.

          First, I assume that you have already added dom4j.jar to your classpath to get past the NoClassDefFoundError exception.

          Second, it would appear that there was a change between 3.2.3 and 4.0.2 that requires dom4j (don't ya hate it when someone states the obvious :-)). An examination of the stack trace that accompanied the exception, in conjunction with and examination of the source code, should shed some light on why dom4j is now being invoked, and might even lead to clues on how to avoid dom4j from being invoked.