Ah... Ignore my previous answer to this, trying to blame Xalan. ;^)
You can add me to the list of those prefering it the old way (the parser
should be application nuetral, and stdout is crucial to console
applications). But I suppose it doesn't really matter since implementing
ErrorHandler takes care of it (which is why I never noticed and
complained). I'd vote for stderr by default over stdout, though.
Eric
Andy Clark
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
g> cc:
Subject: Re: Error output to
console
05/13/2002 09:58
AM
Please respond
to xerces-j-user
"Lemmin, Harald" wrote:
> [Fatal Error] :1:1: Content is not allowed in prolog.
>
> The console output has been added with Xerces 2.
> I do not want it. How can I switch it off?
This was a change that I made for Xerces2 because we were
constantly getting "bug" reports saying that Xerces was
not validating because no errors were printed. This change
eliminates the confusion.
So far you're the first person to actually prefer the
old way. :) But like Gottfried suggested, you can simply
register a no-op error handler to silently ignore the
errors.
--
Andy Clark * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
