The testcase was just added at 4.0.x, shouldn't be different with 3.2.x, but it
uses a scoped .sar not a .war.
Maybe you can try scoping an empty sar, with the new xml jars inside, and the
.war as a nested subdeployment.
View the original post :
Your best bet is to scope your deployment and put the new xalan/xerces version
in there. The 4.0.x has a testcase for this:
org.jboss.test.xslt.test.ScopedXalanUnitTestCase
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938009#3938009
Reply to the post :
Thanks for the response...
I tried to scope the deployment, using the jboss-web.xml file as described at
http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration like this:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE jboss-web PUBLIC -//JBoss//DTD Web Application 2.3//EN
