[jira] Commented: (XERCESC-1789) trailing whitespace on error messages

["Jay Berkenbilt (JIRA)" <xe...@xml.apache.org>]

    [ https://issues.apache.org/jira/browse/XERCESC-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579052#action_12579052 ] 

Jay Berkenbilt commented on XERCESC-1789:
-----------------------------------------

I'm changing the category from SAX to miscellaneous because I observe that the same problem happens with DOMPrint as well.

> trailing whitespace on error messages
> -------------------------------------
>
>                 Key: XERCESC-1789
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1789
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: SAX/SAX2
>    Affects Versions: 3.0.0
>         Environment: debian
>            Reporter: Jay Berkenbilt
>         Attachments: a.err, a.xml
>
>
> In testing the beta of xerces-c 3.0.0 using the automated test suite for some code I have that uses it, I noticed that errors returned by xerces::SAXParseException::getMessage() have trailing whitespace that they did not previously have.
> All of my error condition tests failed because of the trailing whitespace on the messages.
> This is trivial to reproduce.  Just run samples/SAXPrint on an xml file with an error, such as this one:
> <a>
> This results in the following output:
> <?xml version="1.0" encoding="LATIN1"?>
> <a>
> Fatal Error at file /tmp/a.xml, line 2, char 1
>   Message: The input ended before all started tags were ended. Last tag started was 'a' 
> but there is an extraneous blank after the end of the message.  I will attach the input file (a.xml) and the output file (a.err) so you can see this.
> I left the priority as Major of this, but if it were my project, I'd set it as Blocker -- this will have a massive impact on anyone who has automated tests that may include these error messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org