This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Optimizing transform in java
- From: Daniel Fisher <daniel dot fisher at vt dot edu>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Thu, 24 Jan 2002 10:55:43 -0500
- Subject: Re: [xsl] Optimizing transform in java
- Organization: Virginia Tech
- References: <002d01c1a461$20a43560$6fc469d5@pcukmka>
- Reply-to: xsl-list at lists dot mulberrytech dot com
On Wed 23 Jan 02 17:55, you wrote:
> > I've got a few questions about doing XSL transformations in Java.
> > I have an application which stores a JDOM object in memory
> > and transforms the object to HTML for viewing.
> > I'm currently using the Xalan transformer
> > (org.apache.xalan.processor.TransformerFactoryImpl) for the
> > transformation.
> > Is this the best transformer for a JDOM object?
> > It doesn't seem like it would be since it extends
> > javax.xml.transform.sax.SAXTransformerFactory,
> > which is a SAX transformer.
>
> Saxon has built-in support for JDOM transformation, though (as with Xalan)
> it works faster if you let it build its own native tree from SAX input.
>
Ok...since JDOMSource extends SAXSource will this do the trick?
transformer.transform(new JDOMSource(doc), out);
Thanks for your help.
--
Daniel Fisher
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list