Is it possible to make an XSLTProcessor function as a DocumentHan dler?

["Sobeck, David" <da...@thinklinkinc.com>]

I have a series of DOM transformations which eventually feed into an
XSLTProcessor, which proceeds to publish the results as HTML. I am trying to
convert this sequence to SAX in order to avoid the high overhead associated
with multiple DOM Documents, but have reached the following stumbling block:
the input to the XSLTProcessor must be a String, a Stream, or a Node. I
think that I want the XSLTProcessor to function as a ContentHandler. I guess
that I could serialize my output and have the XSLTProcessor reparse it, but
that seems inefficient. I just want some entry point so that I can drive the
processor with SAX event methods.

It looks like all the right methods are present in XSLTEngineImpl, but it is
not declared to implement ContentHandler, and is peppered with dire
warnings.

I feel like I'm missing something obvious.