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=27081>.
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=27081

Too much malformed data is reported

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2004-02-23 19:04 -------
This was a reset bug. Everything reported in Bug #27145 seems to be symptoms of 
the same bug. I'm marking that as a duplicate. The only way I could reproduce 
those results is by first using the parser to read a malformed document which 
would cause the parser to throw an exception while scanning ']'.

Here's what was wrong.

When the parser scans sequences of ']' in character data it appends them to a 
buffer before reporting them in case the section contains an illegal ']]>'. 
While in this section a boolean is set indicating that content is being scanned 
in case the current entity ends. This makes it possible to flush the buffer to 
a characters call before calling endEntity.

If an exception is thrown in this section, this state never gets reset on a new 
parse. The buffer to scan content is also used to scan comments and a few other 
structures. While in this state the parser would report anything currently in 
the buffer as characters at the end of any general entity as well as the 
document entity.

This is fixed in CVS now.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to