1 Reply Latest reply on Jul 1, 2005 5:48 PM by nsakiya

    the order of classpaths

    nsakiya

      I'm running web applications in 'all' configuration, and trying to give each of them their own classloader by configuring the jboss-web.xml as follows:

      <jboss-web>
      <class-loading>
      <loader-repository>
      siras.com:loader=loader1
      <loader-respository-config>
      java2ParentDelegation=false
      </loader-respository-config>
      </loader-repository>
      </class-loading>
      </jboss-web>

      Right after put these in, I got a bunch of errors. They all seem to be jar conflicts. I have many apache 's commons-* jar in my /WEB-INF/lib, though. I wasn't changing anything in jboss/lib or jboss/server/all/lib. They all now confuse me very much. Maybe somebody here can explain to me what classpath my app will go through and in what order with the jboss-web.xml configuration above. And, what is difference if I set java2ParentDelegation to true.

      1. WEB-INF/lib/*
      2. ....
      3. .....

      Thank you very much.