/Michael Glavassevich/:
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 J
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 say
(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 c
/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
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.
Specifically XML 1.0 [2] says:
"It is a fatal error when an XML processor encounters an entity with an
enc
