You are viewing a plain text version of this content. The canonical link for it is here.

Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/09/06 18:25:12 UTC

DO NOT REPLY [Bug 9192] - Total Element Contents Not Parsed

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

Total Element Contents Not Parsed

neilg@ca.ibm.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From neilg@ca.ibm.com  2002-09-06 16:25 -------
This sounds like a common problem people have in expecting SAX characters 
callbacks to contain the entire text content of an element in one shot.  If you 
read the SAX ContentHandler documentation, you'll find that this expectation is 
incorrect--parsers are free to return character content in as many characters 
callbacks as they find convenient, provided it all gets passed back eventually.

If Xerces is indeed missing characters, please reopen this bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org