0 Replies Latest reply on May 31, 2003 2:18 PM by tek1

    Java2ClassLoadingCompliance=false -> ClassCastException

    tek1 Newbie

      Hello all!

      I'm using JBoss 3.2.1 jetty and in JBOSS_HOME/server/default/deploy/jbossweb-jetty.sar/META-INF/jboss-service.xml, when I changed the setting for Java2ClassLoadingCompliance to "false":

      false

      and restarted JBoss, the following ClassCastException was encountered:

      13:57:10,360 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported e
      rror follows.
      13:57:10,360 ERROR [STDERR] java.lang.ClassCastException
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseApp
      ender(DOMConfigurator.java:165)
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppe
      nderByName(DOMConfigurator.java:140)
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppe
      nderByReference(DOMConfigurator.java:153)
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChi
      ldrenOfLoggerElement(DOMConfigurator.java:415)
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoo
      t(DOMConfigurator.java:384)
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DO
      MConfigurator.java:790)
      13:57:10,370 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfig
      ure(DOMConfigurator.java:673)
      ...
      (it goes on and on)


      Background:

      Basically, I'm trying to get my .war to check the .jars in its own .war file before checking the all the .jars loaded by the classloader.

      I've deployed two .ear files (not related to each other), one containing pure EJB stuff and the other just a .war file (deployed it as an .ear because I needed to change the name its context root). The two .ear files do contain some similar .jar files. Before I deployed the EJB .ear file, the war .ear file worked fine. However, after deploying the EJB .ear file, which contains some of the same .jars as the war .ear file, the war .ear is not deploying correctly. It appears as though the war .ear is trying to read information from the .jars in the EJB .ear for some reason. It seemed that changing the class loading attribute for Jetty:

      false

      would solve this problem. Unfortunately, that's when the ClassCastException was encountered.

      Any advice would be greatly appreciated.

      Thank you.