Are you sure it Xerces? I do lot of command line tool stuff with Xerces 2, where I care about a clean stdout, and haven't noticed this. I have however had this problem with Xalan (and have had a bug posted about it for a year or so, and they don't seem to take it seriously enough to fix it). If you're using Xalan it is probably the one spewing the error to stdout.
Eric
"Lemmin, Harald"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
wareag.com> cc:
Subject: Error output to
console
05/13/2002 08:48 AM
Please respond to
xerces-j-user
Hello,
If Xerces recognizes any parseerror it throws SAXParseException as well as
gives some output on the console. For example:
[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?
Kind regards,
Harald
---------------------------------------------------------------------
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]
