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=21471>. 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=21471 ContentHandler SAXExceptions consumed ------- Additional Comments From [EMAIL PROTECTED] 2003-10-06 14:40 ------- Joanne's patch was basically OK, but I am about to attach a slight refinement of her patch. It is already applied to CVS. I modified ElememLiteralResult.execute(). The double nesting of try/catch/finally was getting difficult to follow. The key thing was that one needed to do this: - startElement() - stuff in the middle - endElement() If the startElement() was OK then one should call endElement() for balance, even if the stuff in the middle threw an exception. So this involved saving any exception from the stuff in the middle. The only other changes were to stop catching a SAXException in flushPending() for all serializers, so this just meant dropping a few more try/catch (SAXException) blocks that caught the exception and silently did nothing.
