To my knowledge, Xerces is an XML parser, and Xalan does the XSLT stuff.
Hope you got that right in your book :-).
>I used Xerces to write a custom tag for a JSP book I co-wrote that's coming
out
>in a month or so. The tag looks like this on a JSP, for example:
>
><synd:rdf rdfURL="http://www.slashdot.org/slashdot.rdf"
> xslURI="xml/rdf092.xsl"/>
>
>It's slowed by the initial request for the RDF page, but if you have all
your
>XML and XSL local or in a database, this stuff goes much quicker (but doing
>syndication will always require someone/something to hit the Web for
updates).
>The code is very simple and just uses the Xerces APIs to do the processing.
>
>You could also include the dynamic XML output of one JSP into another JSP
or
>servlet, which could then call XSLT engine APIs and a stylesheet to convert
the
>XML to another type of data.
>
>My main beef about Xerces is that it's 1.5 MB. That's way too big if all
you
>want is a fast, light XSLT engine. But its' free and it's got features and
it
>works well and its very easy to use. James Clark has a lightweight XSLT
>processor:
>
