JBoss class loader boot order is another attempt to figure this out

Question

when I deploy the application on JBoess 5.1, Jboss accepts third-party banks from 3 different additional places that I know of:
1.my-app / WEB-INF / lib
2. [JBoss root] / lib
3. [JBoss root] / server / all / lib

my settings for configuring jboss-web and therefore changing the loading of the JBoss class that I know of are the following:
option1:

<jboss-web> <class-loading> <loader-repository>com.example:archive=unique-archive-name</loader-repository> </class-loading> </jboss-web> 

option 2:

 <jboss-web> <class-loading java2ClassLoadingCompliance="false"> <loader-repository> com.example:archive=unique-archive-name <loader-repository-config>java2ParentDelegation=false</loader-repository-config> </loader-repository> </class-loading> </jboss-web> 

option 3:

 <jboss-web> <class-loading java2ClassLoadingCompliance="true"> <loader-repository> com.example:archive=unique-archive-name <loader-repository-config>java2ParentDelegation=false</loader-repository-config> </loader-repository> </class-loading> </jboss-web> 

when trying these parameters, I had another exception when deploying while trying to use different parameters.
My question is: what is the order of the 3 folders that I mentioned above in each of these options. those JBoss links didn't help me understand the different behavior:
link1
link2

Answer 1

Check out these links:

Solving JBoss 5 class loading problems

use JBossWebClassLoader in JBoss5

JBoss 5 adds the concept of custom metadata files, one of which is jboss-classloading.xml , which allows you to precisely determine how warloadload wars will be built.