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
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?
View the original post :
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
I need Xerces 2.7.1 and Xalan 2.7.0 in a web application. I'm using JBoss
4.0.3sp1 (out-of-the-box) and jdk1.5.0_06.
I have tried putting them in the WEB-INF/lib directory but
org.apache.xalan.Version.getVersion() still reports 2.6.0.
View the original post :
