classloading isolation problem / jboss AS 5.1.0

[berkum]

I have this very simple problem (in appearance) :

App.Ear

     lib

          --> commons-collections3.2.1.jar

     --> War1.war

     --> War2.war

Both war1 and war2 use commons-collections3.2.1.jar (but that is not the point).

There is also an old version of commons-collection in

commons/lib

Whenever I try to access the CollectionUtils.isEmpty method from commons-collections, I get a NoSuchMethodError since this method does not exist in the common/lib/commons-collections.jar.

But I wan't to use the commons-collection3.2.1.jar that I packaged with my application.

I have tried all sorts of things such as :

- jboss-classloading.xml

- manifest.mf

- ear-deployer-jboss-beans.xml

- war-deployers-jboss-beans.xml

- jboss-app.xml

but I could not get anything to work.  Not to say that the documentation for these files is almost inexistent which makes it a dummy "try all possibilities" task.

Some people seem to have succeeded in fixing classloading problems, but I could not.

Can someone explain a basic solution for the above simple case or can someone point me to a thorough official documentation (not just wiki stuff).

Thank you.

[shivanic]

Could you please post the contents of the file jboss-app.xml that you have tested with.

shivani

[berkum]

Of course.

<jboss-app>
<loader-repository>
   ca.xyz:archive=EAR_FILE_NAME.ear
   <loader-repository-config>
      java2ParentDelegation=false
   </loader-repository-config>
</loader-repository> 
</jboss-app>

- I have no idea what ca.xyz should represent.

Thank you,

Alain

[berkum]

Conclusion.

I was able to make things work by first cleaning the project.  There were some dependencies between the 2 wars.

Then, I updated the manifest.mf file for each war to reflect correctly the libraries used (commons-collection was correct at first anyway).

I removed all jboss-* files from the deployment.

I updated the application.xml with the header :

<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5">

Note that in war-deployers-jboss-beans.xml, I have the following configuration :

<property name="java2ClassLoadingCompliance">false</property>