Stanimir Stamenkov <[EMAIL PROTECTED]> wrote on 09/14/2006 04:27:46 AM:
> (I've send the previous incomplete message by accident, sorry.) > > /Michael Glavassevich/: > > > SAXException [1] is thrown because character encoding errors are fatal > > errors (as defined by the XML spec) and SAX says fatal errors are reported > > to the application using that exception. > > Thanks. I'm now clear why encoding errors are reported as > SAXExceptions but again, does it sound sensible to initialize the > cause of the SAXException with the original CharConversionException > so this type of errors are more easily recognized? It wouldn't hurt to wrap it in the SAXException. Note that current implementations of SAXException don't support [1] the JDK 1.4 exception chaining mechanism so you should be calling getException() to get the cause. > Could I file an enhancement request in the Apache JIRA? Sure. > -- > Stanimir > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] [1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6385694 Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
