(OOo 3.0 dropped Xalan for Saxon). The transformation is quite complex: it involves >10 chained XSLT files, including one generated from Schematron...
Is there a way to check the exact value of the max memory option at runtime...? Regards, EB > -----Original Message----- > From: Romain Pelisse [mailto:[email protected]] > Sent: Friday, April 03, 2009 12:05 AM > To: [email protected] > Cc: G. Ken Holman > Subject: Re: Re: [xml-dev] Available memory for XSLT filters > > > Hum, i ran into this kind of issue on > XRadar<http://xradar.sourceforge.net/>, > if possible can you show us XSL ? There maybe a way to reduce memory > consumption by tweaking the algorithm, or simply used instruction such as > xalan:redirect (if availaible) to create file buffer to store intermediate > data... > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
