How to force change jboss class loader method 2

In my previous post there is the first method where you can force jboss to isolate class loader of your web app from server class loader. Here what happen is before adding jars in server classpath, jboss will search jars in your web app classpath. If matching jars or duplicating jars found jboss will give priority to the jars found in your web app’s classpath.

So to achieve this the first method is create an entry in jboss-web.xml which is the jboss specific deployment descriptor. The second method is creating a separate xml file “jboss-classloading.xml” in your app’s “WEB-INF” folder and add the class loading instructions in that file. An example is given below.

<classloading xmlns=”urn:jboss:classloading:1.0”
            name=”MyAPP.war”
            domain=”MyAPP_domain”
            parent-domain=”this is optional”
            parent-first=”false”
            export-all=”NON_EMPTY”
            import-all=”true”>
</classloading>

***** parent daomain is optional.