I am currently looking into the amount of memory being used when Xalan creates a XalanSourceTree from the InputSource when processing a transformation. The application I am using Xalan within has the potential for very large XML files (100+ MB) needing to transformed, and based upon tests I have run, it appears that the tree built within Xalan uses about as much memory as the actual size of the XML file. Is there any way of getting around this and limiting the amount of memory required?
- Re: XalanSourceTree memory usage Mark Northcott
- Re: XalanSourceTree memory usage Joseph_Kesselman
- Re: XalanSourceTree memory usage David_N_Bertoni
