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 Summary: ContentHandler SAXExceptions consumed Product: XalanJ2 Version: 2.5Dx Platform: PC OS/Version: Windows XP Status: NEW Severity: Major Priority: Other Component: org.apache.xalan.transformer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Under certain conditions, throwing a SAXException within a TransformerHandler's resultant ContentHandler can be consumed in order to report subsequent exceptions that should never been thrown. For example, say a call to endElement() caused the ContentHandler to abort processing and enter an illegal state thus throwing a SAXException. Then since it is safe to assume the processing has been aborted and any subsequent calls to endElement() could throw an illegal state SAXException for precaution. This scenario causes the initial exception to be consumed and the second illegal state exception to be reported instead. I've attached the code to reproduce this bug along with the output from EnvironmentCheck. It is worth noting that this does not happen when the identity transformer is used. Also, the number of consumed exceptions increases as the depth of the offending element in the XSL result tree increases, as the example shows.
