On Aug 15, 2007, at 11:42 AM, Edward L. Knoll wrote:
Refer to Sun's documentation on BOOTCLASSPATH. Sun's JVM has
specific versions of some jar files/classpaths which are builtin/
hard-coded and override the standard CLASSPATH. Effectively you
will end up adding the following argument to your java invocations:
-Xbootclasspath/p:filepath:filepath:filepath:....
I haven't tried this in a while, but bootclasspath shouldn't be
needed anymore since JDK 5 where all Apache packages have been
renamed (and now live under com/sun/...). There shouldn't be any more
name clashes as a result. I'd be interested to know if this isn't
working as designed.
In theory, classpath should suffice even without setting the
javax.xml.transform.TransformerFactory property, as it should be read
from xalan.jar if in the classpath.
-- Santiago
On Tue, 2007-08-14 at 13:40 -0400, Santiago Pericas-Geertsen wrote:
On Aug 10, 2007, at 1:22 PM, Mohsen Saboorian wrote:
> On 8/10/07, Zakon, Stuart <[EMAIL PROTECTED]> wrote:
>> We are migrating a web application to JDK 1.5 and have discovered
>> that
>> the XSLT engine is defaulted to Xalan XSLTC:
>> http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/
>> ReleaseNotes_150.html
>>
>> Currently we are experiencing problems with XSLTC and would
like to
>> switch to the interpretive version of Xalan 2.7.
>>
>> In the above release notes and compatability guide it is not clear
>> how
>> we would override this XSLT engine and run the interpretive
>> version of
>> Xalan, even if we install this version outside of the JDK since
>> the JDK
>> takes preference in the classpath.
>>
>
> You should change system properties
> "javax.xml.transform.TransformerFactory", through a call like this:
> System.setProperty("javax.xml.transform.TransformerFactory",
"FQCN");
>
> examples of FQCN:
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
> org.apache.xalan.xsltc.trax.TransformerFactoryImpl
> net.sf.saxon.TransformerFactoryImpl
> gnu.xml.transform.TransformerFactoryImpl
Actually, it should suffice to put Xalan's jar in your classpath,
as the JAXP pluggability layer should search there first.
-- Santiago
