ailto:[EMAIL PROTECTED]
> Sent: Friday, December 20, 2002 1:27 PM
> To: xalan-c-users@xml.apache.org
> Subject: RE: Problems with ProblemListener
>
>
>
>
>
>
> Hi Corey,
>
> I think it's possible in the case of some exceptions to
> report something
> through
t; To: xalan-c-users@xml.apache.org
> Subject: RE: Problems with ProblemListener
>
>
>
>
>
>
> Hi Corey,
>
> I think it's possible in the case of some exceptions to
> report something
> through the ProblemListener interface. The difference would
>
David N
Bertoni/Cambridge/IBM)
Subject: RE: Problems with
ProblemListener
Hi Dave,
> Can you describe in more detail what you're doing, and
> what parts of the current mechanism work for you, and what could be
> improved (aside from obvious requirement of consistent behavior)?
Sure, in my application, which is multi-threaded, I have a framework for
reporting error/d
Hi Corey,
This doesn't surpise me. Error handling is one of the most inconsistent
things in the code, and I've been trying to figure out the best way to
straighten it out. On one hand, the ProblemListener mechanism is nice
because it allows users to plug in special handling. Unfortunately,
