Hi,

Is there a solution how to reduce memory footprint of Xalan? In case I
have a document, that's way too big to process in the memory (eating up
to 6GB of memory with single-process) ?

I'm using TRAX to transform the file these days, so would changing to
StAX-transform solve this issue? My doubt is, that Xalan itself stores
it in the memory.

Or does someone have any better ideas? It's already a split file (from
7GB incoming XML-document..), and can't be splitted to smaller files
anymore in our process. The processing file would be size of ~400MB, and
this seems to eat huge amounts of memory when done with DOM+TRAX
transform.

  - Micke

Reply via email to