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=717>. 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=717 quiet swallowing of exceptions ------- Additional Comments From [EMAIL PROTECTED] 2003-10-18 21:49 ------- Brian: what was the value of EXPLICIT_IDENTITY when you ran it? It should be set to "true" to reproduce the bug. Looks like it's set to "false" in the patch I updated. (An oversight of mine, I guess.) Glad to see someone looking at this problem. I'd be willing to take another stab at fixing it myself, but I'm just not really sure what the correct behavior is according to the spec. I didn't see anything mentioned about what should happen when a ContentHandler throws a RuntimeException or SAXException. Here's the question I asked the mailing list a while ago (with no answer): Is there an authoritative correct behavior when a SAXResult throws an exception (either SAXException or a RuntimeException)? My best guess is: - If you call Transformer.transform, it does an ErrorListener.fatalError(new TransformerException(..., e)). (or error? Is a SAXException from there fatal?) If that's rethrown from there, it must pass through transform back to your code. - If you use it as a TransformerHandler, I'm not sure. Clearly the current behavior (losing all but the message of RuntimeExceptions and ignoring SAXExceptions entirely) is not good, though.
