"David Wall @ Yozons" writes:

> I noted that JDOM has an XSLT processor capability. Does this require
> XALAN or does JDOM have its own implementation of XSLT/transformer?

>From new convenience class XSLTransformer in the lastest CVS:

JDOM relies on TrAX to perform the transformation.
The javax.xml.transform.TransformerFactory Java system property determines
which XSLT engine TrAX uses. Its value should be the fully qualified name
of the implementation of the abstract javax.xml.transform.TransformerFactory
class. Values of this property for popular XSLT processors include:

  * Saxon 6.x: com.icl.saxon.TransformerFactoryImpl
  * Saxon 7.x: net.sf.saxon.TransformerFactoryImpl
  * Xalan: org.apache.xalan.processor.TransformerFactoryImpl
  * jd.xslt: jd.xml.xslt.trax.TransformerFactoryImpl
  * Oracle: oracle.xml.jaxp.JXSAXTransformerFactory

This property can be set in all the usual ways a Java system property can be
set. TrAX picks from them in this order:

 1. Invoking System.setProperty( "javax.xml.transform.TransformerFactory",
   "classname")
 2. The value specified at the command line using the
   -Djavax.xml.transform.TransformerFactory=classname option to the
   java interpreter
 3. The class named in the lib/jaxp.properties properties file in the JRE
   directory, in a line like this one:

      javax.xml.parsers.DocumentBuilderFactory=classname

 4. The class named in the
   META-INF/services/javax.xml.transform.TransformerFactory
   file in the JAR archives available to the runtime
 5. Finally, if all of the above options fail, a default implementation is
   chosen. In Sun's JDK 1.4, this is Xalan 2.2d10.

Brad
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@(protected)