Elliotte Rusty Harold wrote: > 1. Non-fatal errors are printed on System.err
That's the default behavior that we chose after years of people reporting "bugs" saying that Xerces wasn't validating their documents because they didn't see any errors on the output. Now all of those bugs reports and the time required to correct their misconceptions have gone away. :) > 2. If I pass null to parser.setErrorHandler(), I get > NullPointerExceptions when an error is reported That should be corrected. > 3. When I try to throw a custom subclass of SAXParseException out of the > ErrorHandler.error() method, a different exception gets thrown instead. This should be fixable as well. > 2. Is there any way to turn off this unasked for behavior so I can > handle my own errors the way I need to? You can certainly avoid the error output performed by the default installed error handler by registering a no-op error handler of your own. The other problems are probably due to SAX handling initiated from XNI events. So SAX errors get wrapped by XNI errors. But this should be fixable. Anybody with free time to look into this? -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
