ErrorHandler vs. ProblemListener

[Peet Sneekes <pe...@mediamatic.nl>]

Hi,

I was just curious, but why can't I use the ErrorHandler when I use a Xerces
DOMParser?
Now I use a own implementation of the ProblemListener, but I think it's to
limited in giving me information about what went wrong while parsing. When I
use Xalan's XercesLiaison, I can use the ErrorHandler which is much more
detailed in getting error information.

This error information is offered through my program to my (web) designer
friends, which have to deduct the real XML/ XSL problem from that error. The
error I can offer now is just a linenumber and a message. But when the
problem happenes while pprocessing with the XalanLiaison I can get line-,
collumn numbers and much more.

Can anyone give me an answer on this issue?

Cheers,

Peet

Re: ErrorHandler vs. ProblemListener

[Ralf Pfeiffer <rp...@apache.org>]

Peet,
There is no problem using the ErrorHandler with Xerces. I just checked it myself

to make sure it wasn't mysteriously broken.
-rip

Peet Sneekes wrote:

> Hi,
>
> I was just curious, but why can't I use the ErrorHandler when I use a Xerces
> DOMParser?
> Now I use a own implementation of the ProblemListener, but I think it's to
> limited in giving me information about what went wrong while parsing. When I
> use Xalan's XercesLiaison, I can use the ErrorHandler which is much more
> detailed in getting error information.
>
> This error information is offered through my program to my (web) designer
> friends, which have to deduct the real XML/ XSL problem from that error. The
> error I can offer now is just a linenumber and a message. But when the
> problem happenes while pprocessing with the XalanLiaison I can get line-,
> collumn numbers and much more.
>
> Can anyone give me an answer on this issue?
>
> Cheers,
>
> Peet

--
<person name="Ralf I. Pfeiffer" " email="rpfeiffe@apache.org" />