trax is the default.
The problem here is probably because that optional.jar that contains the
liaisons is not in the classpath.
--
St�phane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my
company.
> -----Original Message-----
> From: Shane Curcuru [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 30, 2001 5:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: problems using Xalan-J with ant 1.3 (missing Liaison
> classes)
>
>
> Hmmm - try processor="trax" instead. The "xalan"
> flavor uses the XalanLiaison (I think) which is
> basically usign the Xalan-J 1.x API's. It's much
> better to use the Xalan-J 2.x API's through
> TraXLiaison, which uses javax.xml.transform
>
> - Shane
>
> ---- you S Page <[EMAIL PROTECTED]> wrote ----
> I'm trying to use Xalan-J 2.0.1 with ant 1.3.
>
> If I fork a separate process to invoke Xalan, as
> Xalan-J's own build.xml file does, \
> it works fine:
> <java fork="yes"
> classname="org.apache.xalan.xslt.Process" \
> classpath="${java.class.path}:${build.xalan.jar}">
>
> However, if I try to use ant's built-in <style> task,
> I have problems.
>
> At first, I got
> java.lang.ClassNotFoundException: \
> org.apache.tools.ant.taskdefs.optional.TraXLiaison
> errors.
>
> Then I replaced $ANT_HOME/lib's jaxp.jar and
> parser.jar with the xalan and xerces jar \
> files, as covered in "System Requirement" in the Ant
> User Manual. Now if I use the \
> built-in style command: <style basedir="doc"
> destdir="build/doc"
> processor="xalan"
> extension="html" style="style/apache.xsl"/>
>
> =====
> <eof msg="This is not my regular email account"
> humor="This is not Shane's actual brain today" />
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
>
