DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12962>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12962 Error messages are not user friendly Summary: Error messages are not user friendly Product: Xerces-C++ Version: 2.1.0 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Miscellaneous AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] From: XMLMsgCat_EN_US.Msg 7 An exception occurred! Type:{0}, Message:{1} 156 An exception occurred! Type:{0}, Message:{1} 284 An exception occurred! Type:{0}, Message:{1} 285 Unexpected end of file exception. Message: {0} 45 Datatype error: Type:{0}, Message:{1}. 46 Schema error: Type:{0}, Message:{1} These message are not user friendly. For example I got the following exception: An exception occurred! Type:RuntimeException, Message:The primary document entit y could not be opened. Id=E:\team\review\send\020901\NAG\NagMsg_DTD ( line 0, char 0 ) The first part of the exception "An exception occurred! Type:RuntimeException, Message:" is absolutely informative. Better state smth like: "Parsing exception: The primary document entity could not be opened..." So, the proposal is: 1. Remove all informative text, like "An exception occurred!" 2. Remove template words, like Type: and Message: 3. Provide meaningfull error message As an example compare the following error templates. I think that the second is better. 46 Schema error: Type:{0}, Message:{1} 46 Schema error: {1} --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
