I had the same problems using the new Xalan jars.
Thanks for posting the solution!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3839018#3839018
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839018
It turns out this was an issue with the 1.4.2_03 vm... I had the wrong jar in it's
build.
This is related to other posts here and I found the answer through them.
Sorry for the erroneous post.
The fix from another thread:
anonymous wrote :
| Isolate your application's classloaders from the
Well, loader-repository causes other problems (ClassCastExceptions on the xml-apis
when parsing the deployment descriptors).
Is it possible to use a newer version of xalan with JBoss 3.2.3?
http://www.jboss.org/index.html?module=bbop=viewtopict=33184
From the above link it appears it maybe
We had exactly the same problem when switching to Xalan 2.6 and I am almost sure that
this is an issue with Xalan which does not seem to accept null values in template
parameters (previous versions did).
When the JBoss XSLSubDeployer tries to transform the xxx-ds.xml by providing a null
value
Thank you so much wdrai. It works like a charm.
Info for anyone interested in getting xalan 2.6 to work on jboss 3.2.3:
Copy xalan.jar, xercesImpl.jar, xml-apis.jar to JAVA_HOME/lib/endorsed, and
JAVA_HOME/jre/lib/endorsed.
Specify the -Dboss.server.data.dir=/path/to/server/data system
