0 Replies Latest reply on Mar 3, 2003 2:33 PM by Ryan Hoegg

    Scoped ClassLoader problems with JBoss internal classes

    Ryan Hoegg Newbie

      Hello,

      I am trying to use the scoped classloader feature of the EARDeployer by creating a jboss-app.xml in the META-INF/ subdirectory of my EAR. My jboss-app.xml looks like this:
      <jboss-app>
      <loader-repository>Myapp.com:loader=myapp.ear</loader-repository>
      </jboss-app>

      I think JBoss's parent classloader is still being used. I have a JAR containing Xalan version 1.2.2 in the lib/ subdirectory of my EAR and am referencing it in my EJB and WAR files manifest classpaths. When I try to run code using this, I get a NoSuchMethodError for org.apache.xalan.xslt.Process.getDefaultLiaison(). This method is present in Xalan 1.2.2.

      Also, the log4j.properties I include in my EAR specifies a DEBUG level for the root category. When I deploy this EAR, JBoss starts logging at the DEBUG level on the console for its internal activities.

      These things lead me to believe that JBoss's UCL is being used to load all the classes in my EAR despite my <loader-repository> usage. Is my understanding of this feature broken, or is it JBoss's implementation?

      I have the same results using JBoss 3.0.4 and JBoss 3.0.6.

      Thanks for any insights.