Subject: RE: [xsl] issues with Saxon TRAX support? From: "Michael Kay" <mhkay@xxxxxxxxxxxx> Date: Fri, 20 Jul 2001 06:39:38 +0100 |
I haven't had any memory leak problems reported for a long while. But they are always possible: and not easy to debug. You may need to get hold of a Java monitoring tool to find out which created objects are accumulating. It's best to raise this on the saxon-help list at http://saxon.sourceforge.net/ Mike Kay Software AG > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Paul Brown > Sent: 19 July 2001 22:23 > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: [xsl] issues with Saxon TRAX support? > > > > Are there any known issues with Saxon 6.4's TRAX support? > Running SAXSource > (custom, not an XML parser) -> Transformer -> SAXResult > (org.xml.sax.helpers.DefaultHandler) with a Transformer > generated from a > compiled Templates object results in a memory overflow after > about 10,000 > iterations of the same transformation. > > The code runs without issue through XalanJ2.2.D6. > > -- Paul > > PS FWIW, the two processors are comparable (+/-5%) in speed for my > applications so far. > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] issues with Saxon TRAX suppor, Paul Brown | Thread | [xsl] Element Existence, Alex Genis |
Re: [xsl] newline white space, Lisa Rupe | Date | RE: [xsl] position within same node, Michael Kay |
Month |