Subject: RE: [xsl] SAX for XSL Transformation From: "santhosh nair" <santhosh_as@xxxxxxxxxxx> Date: Fri, 18 Feb 2005 12:22:44 -0800 |
From: "Michael Kay" <mike@xxxxxxxxxxxx> Reply-To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: RE: [xsl] SAX for XSL Transformation Date: Thu, 17 Feb 2005 22:19:50 -0000
Although you can supply a SAXSource as the input to your transformation, the
XSLT engine will generally build a tree in memory. This will usually be much
more efficient than a DOM tree, but it will still be a tree.
> I'm trying to transform a 80M > file using an XSL stylesheet to an output stream.
80M is feasible but challenging. You should allocate at least 512M of memory
to the java VM (use -Xmx512M).
> I'm assuming that the JAXP API uses a DOM object to do this > transformation.
The JAXP API is just an API. What actually happens internally depends on which implementation of the JAXP API you are using, e.g. Xalan, Saxon, Oracle.
Michael Kay http://www.saxonica.com/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] SAX for XSL Transformatio, Michael Kay | Thread | [xsl] xpath predicate help, McKinstry, Scott A |
[xsl] & and & issue, Charles Ohana | Date | Re: [xsl] Adding element to xml sni, Joris Gillis |
Month |