[
https://issues.apache.org/jira/browse/XERCESC-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1558.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.1
Not sure if this is still an issue in 3.0.1. If so, please reopen.
> Review Error Message categories
> -------------------------------
>
> Key: XERCESC-1558
> URL: https://issues.apache.org/jira/browse/XERCESC-1558
> Project: Xerces-C++
> Issue Type: Task
> Components: Miscellaneous
> Reporter: cargilld
> Fix For: 3.0.1
>
>
> Fixes have been made recently to the 2.7 and 3.0 branch to report the actual
> errorCode of a message instead of
> XMLErrs::DisplayErrorMessage. Before the fix, the code was catching an
> exception and then emitting a new error with the XMLErrs::DisplayErrorMessage
> which took the message text from the original error. This means that the
> original errorCode was lost (ie. all errors are displayed as
> XMLErrs::DisplayErrorMessage). The change allows the original errorCode to
> be used. The fixed routine in void XSDErrorReporter::emitError(const
> XMLException& except, const Locator* const aLocator) originally also took
> the errorType off of the exception. However, this resulted in a number of
> messages being emitted as fatal errors instead of errors
> (XMLErrs:DisplayErrorMessage is an error not a fatal error). If the original
> messages were meant to be errors instead of fatal errors then the message
> file should be updated so that they are in the correct category.
--
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-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
