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=15847>. 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=15847 XMLEntityManager$ScannedEntity.scanData cannot handle 1 char delimiter Summary: XMLEntityManager$ScannedEntity.scanData cannot handle 1 char delimiter Product: Xerces2-J Version: 2.2.1 Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: SAX AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Entering the Method with either no data read, or all bytes consumed (fCurrentEntity.position == fCurrentEntity.count, tested at line 2924) causes data to be loaded at position 0 in fCurrentEntity. When fCurrentEntity cannot read in chunks, one character is read. This leaves fCurrentEntity.position == 0 and fCurrentEntity.count == 1. test at line 2933: if (fCurrentEntity.position >= fCurrentEntity.count - delimLen) is commented as searching for an error ("// something must be wrong with the input: e.g., file ends an unterminated comment") but the condition is now TRUE for delimiter length of 1. The result is that the entity is incorrectly parsed and reading the input is now out of sync. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
