Scott & Gulli,
Scott wrote:
> > This does not
> > make sense as the input to the transformation is passed to
> > the TransformHandler as SAX events and not as a Source obj.
>
> I don't understand this statement.
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. Hmmm... don't know if this is
much clearer, really. Sure, it is not that important.
Scott wrote:
> > I have choosen to run the transformation in whatever method
> > is called _last_ of endDocument() and setResult()
>
> I think the best thing to do is for both of us to throw an exception if
> setResult hasn't been called at the point of startDocument. It's better to
> be rigid about this.
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. In the absence of
> a clear specification, I suggest consistency with that behavior.
> And I would say it should be an error if endDocument is called
> when the result target is unspecified (unless there is some
> other meaningful behavior to specify ... I can't think of any).
Good! I have changed the behaviour of the XSLTC TrAX implementation
accordingly. This restraint makes sense, and it also makes sense to
have all the Xalan code behave the same in this respect.
Morten
