http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2659 *** shadow/2659 Tue Jul 17 13:39:07 2001 --- shadow/2659.tmp.28326 Fri Jul 20 13:04:02 2001 *************** *** 3,11 **** +----------------------------------------------------------------------------+ | Bug #: 2659 Product: Xerces-C++ | | Status: NEW Version: 1.5 | ! | Resolution: Platform: Other | ! | Severity: Major OS/Version: Other | ! | Priority: Other Component: Validating Parser (Sche | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | --- 3,11 ---- +----------------------------------------------------------------------------+ | Bug #: 2659 Product: Xerces-C++ | | Status: NEW Version: 1.5 | ! | Resolution: Platform: All | ! | Severity: Critical OS/Version: All | ! | Priority: High Component: Validating Parser (Sche | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | *************** *** 27,30 **** will see that the exception is caught and not propagated. I think this is a bug but you may disagree so I have made the severity major rather than critical or blocker ( which it is for us ). Please feel free to contact me for further ! information. Thanks, guys , much appreciated --- 27,40 ---- will see that the exception is caught and not propagated. I think this is a bug but you may disagree so I have made the severity major rather than critical or blocker ( which it is for us ). Please feel free to contact me for further ! information. Thanks, guys , much appreciated ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-07-20 13:04 ------- ! Hi, I've decided to raise the priority and severity of this error because after ! doing a bunch of reading it seems that it is normal to raise an Exception in ! the SAX callbacks if you want to abort the parse. This tecnique is documented ! in several books I have looked at including Wroxs. Professional XML. I guess ! you guys are the definitive reference but I believe this new behavior in xerces ! 1.5 prevents the parse being terminated before the end of the file is reached. ! I have searched the documentation for another means of stopping the parse but ! there doesn't seem to be one. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
