Also relevant to this is an excellent article by Tony Coates:



http://www.xml.com/pub/a/2002/12/11/ant-xml.html



"Running Multiple XSLT Engines with Ant"



"With mtxslt, it is possible to ignore the value of the Java 
javax.xml.transform.TransformerFactory property and simply load a 
particular XSLT engine directly."



It predates the very latest Saxon, but since it is designed to allow 
folding new processors in, it ought to work. (It does require you to 
install and run an 'mtxslt' Ant task, which is on Sourceforge.)



Cheers,
Wendell

At 05:53 PM 2/1/2005, Mike wrote:
The spec says the processor attribute is:



name of the XSLT processor to use. Permissible values are "trax" for a TraX
compliant processor (ie JAXP interface implementation such as Xalan 2 or
Saxon), "xslp" for the XSL:P processor, "xalan" for the Apache XML Xalan
(version 1) processor the name of an arbitrary XSLTLiaison class. Defaults
to trax, followed by xalan and then xslp (in that order). The first one
found in your class path is the one that is used. DEPRECATED - XSL:P and
xalan are deprecated and no more supported..

That suggests you should use "trax", and then make sure Saxon is selected by
setting your classpath or system properties accordingly. Presumably Ant has
tried to load the class and cast it to an "XSLTLiaison" - seems an
unfriendly way of failing.




======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================