You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2003/02/21 18:08:18 UTC
DO NOT REPLY [Bug 17294] New: -
Incorrect params in InvalidCharInAttValue and usage in reportFatalError()
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: xerces-j-dev@xml.apache.org
ReportedBy: matja@seznam.cz
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org