Hello, I'm parsing a large xml file using the saxon xslt parser, generating an even larger xml file which I write out to disk.
Problem is that OXF seems to create an in-memory model of the results, which it does not release after the file has been written out. 2 questions: ------------ 1. Is there any way to make sure that OXF never builds an in-memory model (DOM, I presume), for an xslt transformation? 2. If not, is there a way to make sure that this model is not cached? I'll be doing several transformations on large xml files, so a low memory footprint will be of great importance. Cocoon handles this by sending sax events down the pipeline. How about OXF? Thanks for your help. Henrik _______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
