I agree, error and warning messages should be very point of fact containing as much pertinent information as possible without any fluff. Perhaps the following format would be better to allow grep'ing of all ^[ERROR|WARNING|INFO|DEBUG|FATAL] in log files.
[ERROR|WARNING|INFO|DEBUG|FATAL]: "Msg text here" Regards, Nicholas -----Original Message----- From: Boris Kolpackov [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 5:51 AM To: [email protected] Subject: Changes to some error messages Hi, Some of the diagnostics messages reported via the ErrorHandler interface have the prefix in the form "An exception occurred! Type:RuntimeException, Message:", for example: "An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/tmp/test.xml" I would like to remove this prefix for the following reasons: 1. I get this error or warning via the error handler interface, along with things like XML well-formedness and XML Schema validation errors. The fact that this error is internally represented as an exception and its type don't add any useful information to the message. These are implementation details of Xerces-C++. 2. It is inconsistent with the way other errors and warning (e.g., XML, XML Schema, etc.) are formatted. 3. It is ugly. I personally don't like any exclamation marks in the diagnostics that my applications produce). Let me know if you have any objections. Boris --------------------------------------------------------------------- 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]
