[XERCESJ-625] Incorrect params in InvalidCharInAttValue and usage in reportFatalError()

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Component/s: SAX
• Environment: Operating System: All; Platform: All
• Bugzilla Id: 17294
• Assignee: Venugopal Rao K
• Reporter: MaT
• Created: 22/Feb/03 01:08
• Updated: 13/Apr/04 01:28
• Resolved: 13/Apr/04 01:28

Description

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