Adam Jenkins schrieb:
Try to avoid the temptation to force XSLT into using stateful
non-XSLT objects
Yep, understood, unfortunately the 'best practice' way of doing what I
need to do (large multi document xslt processing block) is just way
too memory intensive due to recursion requirements.
We initial had a standard solution as you suggest, which worked fine,
but required over 3Gb of memory!
That's undesirable, of course. But perhaps you can avoid such excessive
memory consumption by writing a SAX filter that yields a view of only the
relevant portions of your documents by discarding the rest. You could
register a URI resolver and then access your documents using something
like document('sax://doc.xml'). That has the potential to dramatically
reduce memory consumption. But the degree of feasability depends on the
particularities of your situation.
Michael Ludwig
