Morten Jorgensen <[EMAIL PROTECTED]> wrote:
> Yes, it is a bit of a mess. I was trying to say that it would not
> make sense to call transform() on the Transformer (ie. passing it
> a Source object) when the source document is passed to the
> TransformerHandler using SAX events.
Thinking about it a bit more... TransformerHandler is really just meant as
an event handler for the transformer. If you did get a Transformer from
the TransformerHandler, and then called t.transform(source, result), it
should probably just work, even though it wouldn't make much sense to do
things this way.
Gunnlaugur Thor Briem wrote:
> TransformerHandlerImpl for Xalan-J (regular) simply sets the
> ContentHandler for the result in setResult, and performs the
> transformation when endDocument is called.
This is actually not true if it is set up for incremental transform. In
this case, the transform begins in startDocument on a second thread. When
the transformer needs more nodes, it will hang out waiting for the main
thread (TransformerHandler events) to build more of the source tree.
-scott
