I have tried the 'isolation' and the 'isolation with overriding' configuration - but none of those have any effect on Xalan and Xerces specificly.
I still get Xalan version 2.6.0 and Xerces version 2.7.0 from my servlets.
Is it possible at all?
If your application is packaged as an ear with classloader isolation, then have the entries similar to the following in the application.xml(present in META-INF):
<module> <java>xerces.jar</java> </module> <module> <java>xalan.jar</java> </module>
Place these 2 jars directly under your .ear
I still can't get it to work. I have an ear-archive with a isolated overriding classloader. I still get Xalan version 2.6.0 when i hit the url http://localhost:8080/jbossclass/version.
I have constructed a small example that demonstrates my problem. The example builds an ear with one war and xerces and xalan in it.
I'm using jdk 1.5.0_06, ant 1.6.2 and jboss 4.0.3sp1.
The example is available here: http://www.muh-ko.dk/jbossclass.zip (~12kb)
My solution is to move xalan.jar from lib/endorsed to server/default/lib (http://jira.jboss.com/jira/browse/JBAS-2073) and live with Xerces 2.7.0 from lib/endorsed. JBoss cannot start if Xerces is not in lib/endorsed.
If i run into troubles with this Xerces version i will put Xerces 2.7.1 in lib/endorsed and cross my fingers that JBoss will work with this version of Xerces.
Hey i had the same problems. And found a solution for our problem.
I don't know which xerces and xalan we are using though.
What we did:
I renamed the jars in the endorsed library to:
Then i renamed our xalan and xerces to the folowing:
Note that our jboss is only configure with folowing items since we don't need the rest. I don't know what jboss does when you need something else.
... OUR WAR's
I hope this helps
Best of luck.
If something is unclear ask away.