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:56:29 UTC
DO NOT REPLY [Bug 17294] -
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()
------- Additional Comments From gmarcy@us.ibm.com 2003-02-21 17:56 -------
Actually, the orginal message is correct, the call site is wrong.
the correct call is:
reportFatalError("InvalidCharInAttValue",
new Object[] {null, atName, Integer.toString(c, 16)});
The method from Xerces 1 (where these messages first came from) had the element
name passed as a parameter when scanning attribute values so that all error
messages relating to attribute errors could include the element name and the
attribute name. While the element name doesn't happen to be used in the
current message, it was always intended that the reportFatalError callee have
access to the element name if desired. The use of null in these cases to work
around the missing element name is unfortunate and it would be nice if someone
would fix it so that the parameters were available as intended.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org