Skip to Content.
Sympa Menu

xom-interest - RE: [XOM-interest] XSLTransform constructors are flawed

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: "McEniry, Michael" <mmceniry AT itsc.uah.edu>
  • To: <xom-interest AT lists.ibiblio.org>
  • Subject: RE: [XOM-interest] XSLTransform constructors are flawed
  • Date: Sat, 4 Sep 2004 07:49:05 -0500

To avoid an extra text-parsing step:

Option 1: A custom Source implementation (XOMSource?). Probably best to
derive from SAXSource. JDOM does this with JDOMSource.

Option 2: Use SAXConverter (somehow?) to feed a SAXSource.

-----Original Message-----
From: xom-interest-bounces AT lists.ibiblio.org
[mailto:xom-interest-bounces AT lists.ibiblio.org] On Behalf Of Elliotte
Rusty Harold

When a Document object is passed to an XSLTransform constructor it is
written into a StringBuffer which is then passed to TrAX as a
StringReader. Thus it gets parsed twice. In any case, it is more
efficient just to pass in the Reader/InputStream/File/URL rather than
a Document.

Anyway, that's what I'm thinking now. If I can figure out how to
avoid the double parse in the XSLTransform(Document) constructor I
may change this again; but at least two of the constructors are
sticking around for the time being.




Archive powered by MHonArc 2.6.24.

Top of Page