[
https://issues.apache.org/jira/browse/XERCESC-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579053#action_12579053
]
Jay Berkenbilt commented on XERCESC-1789:
-----------------------------------------
I should mention that make check run on xerces-c indicates a passing test
suite, though I can't see a lot of error messages in the test cases!
> trailing whitespace on error messages
> -------------------------------------
>
> Key: XERCESC-1789
> URL: https://issues.apache.org/jira/browse/XERCESC-1789
> Project: Xerces-C++
> Issue Type: Bug
> Components: Miscellaneous
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
