war classloading issue on jboss-4.0.0

[dhill]

I am trying to deploy a war to the default server using the isolation methods described in the classloading docs, the issue I am having is that we use a diff version of castor than what is shipped with jboss-4.0.0, I have tried the isolation methods but it seems that once the castor.jar from server/default/lib is accessed it is placed on a classloader that seems to be the parent of the war, the class is loaded in the jboss-4.0.0\server\default\deploy\ebxmlrr-service.sar\ebxmlrr.war servlet, so when I try to call my version, the classes are already loaded and hence I get a ClassCastException, how do I get around this issue, do I need to create a subclass or my own LoaderRepository, any thought or suggestions would be helpful.

[starksm64]

Unless you want to use jaxr, you can just remove the existing castor jar and ebxmlrr-service.sar.

Where are you putting the castor jar and what does your jboss-web.xml look like?

[dhill]

I am putting the castor jar in war/WEB-INF/lib and here is my jboss-web.xml
<class-loading java2ClassLoadingCompliance='false'>
<loader-repository>
test.com:loader=portal.war
<loader-repository-config>
java2ParentDelegaton=false
</loader-repository-config>
</loader-repository>
</class-loading>

I know if I remove the jar from server/default/lib it works but a client may want to use jaxr in this config.

.don

[starksm64]

Then post a bug to sourceforge with an example war illustrating the class conflict and I'll look at it.

http://sourceforge.net/tracker/?group_id=22866&atid=376685