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=5636>. 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=5636 ArrayIndexOutOfBoundsException in TransformerImpl when using TransformerHandler as ContentHandler for custom XMLReader instances [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-01-03 08:15 ------- The obvious difference, of course, is that rather than using the parser to read the input you're generating a SAX stream programmatically. If I switch back to using the parser, we're fine. (Yes, I changed the xmlGoodStr to agree with the document you're attempting to synthesize as SAX events.) So what's different about the SAX events in the two cases? One obvious difference is that you are passing in "" as the localname on the startElement/endElement calls. I believe that leaving localname blank is is a misuse of SAX. Any given SAX application may or may not be sensitive to it, depending on whether it uses that field. In the past we didn't; now we do. So the bug is in the user's code, not in Xalan. Correcting it eliminates the error.
