DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1205>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1205 TransformerHandler not reusable [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Priority|Medium |Other ------- Additional Comments From [EMAIL PROTECTED] 2001-10-04 15:33 ------- Although I can see the comparison with Transformers (which clearly are meant to be reused) I think the more apt comparison is with a SAX ContentHandler, which generally are not reused - at least not without someone providing a reset() on their implementation of ContentHandler, which JAXP doesn't do. There are two potential questions here: -- JAXP should perhaps document the specified behavior of TransformerHandlers in their next release. That's beyond our control, you need to look at http://java.sun.com/xml/jaxp.html if you want to influence JAXP itself (which Sun and the JCP own). -- Xalan should be polite and let the user know that their TransformerHandler is no longer 'listening' after the endDocument() call. I'd consider this a useful enhancement to xalan, but not necessarily a very high priority (compared to a few other things on our list. Changed Pri/Sev to match.
