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.
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.
1 of 1 people found this helpful
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.
(These are probably the EAP versions, you might want to check in your particular distribution)
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.
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!