> creates a DOM out of it, then does an XSLT transform to html.
At this time, I think you'll get better performance if your application
creates a SAX stream and let Xalan build its own internal representation
before doing the transformation... especially for large documents and
stylesheets that may not need to scan the entire input, where the
incremental mode may be particularly valuable.
(Basically: If you feed Xalan a SAX stream, it builds a direct
implementation of DTM. If you feed it a DOM, it has to wrap a DTM proxy
around your DOM.)
