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=4381>. 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=4381 Progressive parse scan token is not being reset after parseFirst() encounters a warning, which makes the token passed no longer valid Summary: Progressive parse scan token is not being reset after parseFirst() encounters a warning, which makes the token passed no longer valid Product: Xerces-C++ Version: 1.4 Platform: PC OS/Version: Windows 9x Status: NEW Severity: Major Priority: Other Component: SAX/SAX2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] parseFirst() returns "TRUE" when there is a warning but the scan token is now not valid and as a result, any subsequent parseNext() always fails. Here's my email to the newsgroup: Hi Everyone, I'm currently using the SAXParser and I'm getting warnings when my encoding scheme stated does not match the actual encoding in the document.� This is good.� However, when I attempt a parseNext(token) after the warning, I get an error code 68 which is "Scan_BadPScanToken".� This is because the XMLPScanToken passed to parseNext() still has both the fScannerId and fSequenceId as 0 (zero) while the internal fScannerId and fSequenceId in XMLScanner is something other than zero. Isn't my XMLPScanToken passed to parseFirst() supposed to be loaded with the new info from the XMLScanner regardless of whether I get an error in the prolog or not?� In my case, it is still zero and causes a subsequent error when I parseNext(). Or is the internal fScannerId and fSequenceId in XMLScanner suppose to reinitialize back to zero after a warning so that I can avoid subsequent errors after a warning? How do I keep my token in sync with the XMLScanner token?� Here's Dean Roddey's response: If parseFirst() returns false, then you can't go any further and in that case it wouldn't have probably set up the token. If parseFirst() is returning true, and you are seeing this problem, then that's probably a bug. � --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
