What I'm saying is under jdk1.4 the only way to override the jdk
embedded xalan with a different version is to drop it in lib/endorsed or
use a scoped deployment.
Putting it in server/xxx/lib or server/xxx/deploy won't work, even if
specifying the javax.xml.transform.TransformerFactory property
]
[mailto:[EMAIL PROTECTED] On
Behalf Of Dimitris Andreadis
Sent: Monday, February 20, 2006 12:39 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] FW: [JBoss JIRA] Updated:
(JBAS-2073) Remove xalan.jar from ./lib/endorsed
What I'm saying is under jdk1.4 the only
So the problem is lack of encapsulation of the essentially
global org.apache.xalan.processor.TransformFactoryImpl name
due to the proliferation of the xalan distribution. One
should be able to work around this by introducing a
org.apache.xalan.processor.TransformFactoryImpl2 that loaded
The org.apache.xalan.processor.TransformFactoryImpl visible
through the TCL, for a non-scoped deployment, wouldn't be
again the JDK bundled xalan, since this is loaded with the
Bootstrap CL? (testing my CL knowledge here :)
Not necessarily because the org.apache.* is not a jdk core
