JBoss 5.1 endorsed library conflicts

[rise.uday]

Hi, I am upgrading a set of products from JBoss327 to JBoss5.1, the products use JAXB (jaxb-rt-1.0-ea.jar) and xercesImpl-1.0.jar

i compiled the products using endorced directory machinism provided by Java, however on deployment i realised that the JBoss itself uses different versions of same apis as its endorced machenism (it is being used in start-up modules of JBoss).

i seek help to resolve this issue, how can i use my version of Jars?

[sfcoy]

I think your time will be better spent updating to JAXB 2.1 and the JAXP implementation provided by JBoss 5.1. If you try to override these mechanisms with older implementations the whole application server is unlikely to work properly.

[rise.uday]

Thanks Stephen for your suggestion, I want to use the approach of upgrading to JAXB 2.1 as last option, I have used machenisms which allow war files to have explicit classloaders (jboss-classloading.xml),

is there similar kind of machenism to override classloader for ear deploment? any link will help, I have been googling since last 2 days but not able to find a location where things are elaborate enough.

Thanks in advance.

[sfcoy]

The last time that I had to figure out what to put in a jboss-classloading.xml file, I looked it up in the JBoss source.

See http://anonsvn.jboss.org/repos/jbossas/projects/jboss-deployers/tags/2.0.10.GA and http://anonsvn.jboss.org/repos/jbossas/projects/jboss-cl/tags/2.0.9.GA.

(These are probably the EAP versions, you might want to check in your particular distribution)

[rise.uday]

Thanks Stephen for your sincier advice.

I finally realised that it is a bug in JBoss5.1 which was later fixed in JBoss6.0M2 (the issue with xercesImpl jar), however upgrading JAXB is inevitable, as it is still there in endorsed dir of JBoss lib folder.

References:

https://community.jboss.org/wiki/WhydoigetjavalangClassCastExceptionorgapachexercesparsersXIncludeAwareParserConfigurationinAS-5#comment-9724

https://issues.jboss.org/browse/JBAS-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel#issue-tabs

jboss-classloading.xml will work for every API other than what is there in endorsed folder of a JBoss distribution.

please review my understanding and let me know if I am thinking in right direction!