I've noticed with the latest Xerces 2.0.2 that it seems to be using its own ErrorHandler when I'm parsing a document with SAX, which gets in the way of SAX's own ErrorHandler. In particular:
1. Non-fatal errors are printed on System.err 2. If I pass null to parser.setErrorHandler(), I get NullPointerExceptions when an error is reported 3. When I try to throw a custom subclass of SAXParseException out of the ErrorHandler.error() method, a different exception gets thrown instead. In other words, it feels that Xerces is being overly aggressive and going beyond what the SAX spec says it will do. Two questions: 1. is this deliberate? Doe sit sound familair to anyone? Or have I perhaps misdiagnosed the source of my problem? 2. Is there any way to turn off this unasked for behavior so I can handle my own errors the way I need to? -- Elliotte --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
