-
1. Re: classloading isolation problem / jboss AS 5.1.0
shivanic Jul 8, 2010 12:41 AM (in response to berkum)Could you please post the contents of the file jboss-app.xml that you have tested with.
shivani
-
2. Re: classloading isolation problem / jboss AS 5.1.0
berkum Jul 9, 2010 9:11 AM (in response to shivanic)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
-
3. Re: classloading isolation problem / jboss AS 5.1.0
berkum Jul 19, 2010 2:35 PM (in response to 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>