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=17294>. 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=17294 Incorrect params in InvalidCharInAttValue and usage in reportFatalError() Summary: Incorrect params in InvalidCharInAttValue and usage in reportFatalError() Product: Xerces2-J Version: 2.3.0 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: SAX AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This bug is present in all versions 2.0.0 - 2.3.0 ------------------------------------------------- props file XMLMessages.properties contains incorrect definition of InvalidCharInAttValue = An invalid XML character (Unicode: 0x{2}) was found in the value of attribute \"{1}\". correct is: InvalidCharInAttValue = An invalid XML character (Unicode: 0x{0}) was found in the value of attribute \"{1}\". On occurence of this error in XML11DocumentScannerImpl.java and XMLScanner.java only one param value is passed: reportFatalError("InvalidCharInAttValue", new Object[] {Integer.toString(c, 16)}); correct call is: reportFatalError("InvalidCharInAttValue", new Object[] {Integer.toString(c, 16), atName}); MaT --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
