Subject: RE: SAX for XSL Transformation
From: "santhosh nair" <santhosh_as@xxxxxxxxxxx>
Date: Fri, 18 Feb 2005 12:22:44 -0800
|
Thanks Michael, I already had -Xms256m -Xmx512m. But the problem was , when
memory is low n the system , I was getting
Cannot allocate memory for initializeMarkAndAllocBits(allocbits1).
I will try to get the xsl transformation to be compiled ta class and try
again.
BTW the J2SE 1.4 from IBM was using the Xalan implementation.
Santhosh.
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Reply-To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: 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/
|
Cart
