|
|
(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? Could I file an
enhancement request in the Apache JIRA?
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: j-users-help@xxxxxxxxxxxxxxxxx
|
|