Hi,
I brought up this issue before.
When I already have a DOM at hand, there are two ways to pass it to
Xalan:
1) passes it directly to Xalan as DOMSource;
2) traverses the DOM tree and manually fires the SAX events into Xalan
(TransformerHandler).
>From previous discussion, the (1) should be both faster and consumes
smaller memory footprint since with (2), Xalan will build another
internal DTM.
While I ran some tests on both cases, it turned out (2) is still faster
than (1), while it's true it commands more memory.
Is this because the DTM is especially optimized for SAXSource? DOM2DTM
wrapping slows down the transformation indeed?
Thanks.
Li Liang
