Hi,
I have a question about the SAXSource and DOMSource under the context of
DTM.
Is it true when the source is SAX events, Xalan will still need to build
an internal source tree for the transformation? Now the internal tree
representation is DTM, done by SAX2DTM?
So if the source is DOM, will Xalan use this tree directly, or build
another internal representation in DTM? If I understand right, DOM2DTM
is only a wrapper that the same DOM tree can be accessed via DTM
interface, right?
Has anybody benchmarked the performance of SAXSource and DOMSource under
the new DTM implementation?
1. I have a DOM, use a custom DOM2SAX serializer to traverse the tree,
fire SAX events to Xalan.
2. With the same DOM, pass the DOMSource directly to Xalan.
Which case will be faster, consume less memory?
Another question is about the Result, does Xalan fire the result SAX
events in any way, then depend on the Result, it will pass the SAX
events, build DOM, or serialize to Stream, respectively?
Thanks a lot.
Li
