You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Petr Kuzel <Pe...@sun.com> on 2001/05/06 18:50:09 UTC

Xerces2 callback error reporting

Hi,

I have one suggestion about error reporting that can be implemented
in Xerces2. Nowadays I can choose that parser will survive fatal errors.
That is good. But may handle want to choose what fatal error should
be survived. The handler get SAXParserException through fatalError()
callback with no additional information.

There could well known exception subclasses allowing to get more info
or simply decide according to the exception class.

Particularly I am looking forward SAXEntityNotDeclaredException so
I can selectively survive this kind of fatal error only.

  Cc.

-- 
<address>
<a href="mailto:pkuzel@netbeans.com">Petr Kuzel</a>, Sun Microsystems
: <a href="http://www.sun.com/forte/ffj/ie/">Forte Tools</a>
: XML and <a href="http://jini.netbeans.org/">Jini</a> modules</address>

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org


Re: Xerces2 callback error reporting

Posted by Andy Clark <an...@apache.org>.
Petr Kuzel wrote:
> There could well known exception subclasses allowing to get more info
> or simply decide according to the exception class.

The only problem is that there are *so* many kinds of errors
that making individual exception classes for them would not
be advisable. And if you open the door to a limited number
of errors, then you have people requesting their favorites
and the tidal wave has begun...

But, like everything else, this is open to discussion. What
do other people think?

-- 
Andy Clark * IBM, TRL - Japan * andyc@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org