[
http://nagoya.apache.org/jira/browse/XERCESJ-1028?page=comments#action_55329 ]
Jeff Suttor commented on XERCESJ-1028:
--------------------------------------
Michael Glavassevich is correct that the root cause of this is the lack of
registering a Message Formatter for domain in which the errors occur.
registering a Message Formatter:
// format error message with Schema aware formatter
errorReporter.putMessageFormatter(
XSMessageFormatter.SCHEMA_DOMAIN,
new XSMessageFormatter()
);
outputs an error message in the expected format.
this issue can be closed.
> URIs in error messages are incorrect
> ------------------------------------
>
> Key: XERCESJ-1028
> URL: http://nagoya.apache.org/jira/browse/XERCESJ-1028
> Project: Xerces2-J
> Type: Bug
> Components: Other
> Versions: 2.6.2
> Reporter: Jeff Suttor
> Priority: Minor
>
> the URI provided in error messages are incorrect.
> e.g.:
> org.xml.sax.SAXParseException:
> http://www.w3.org/TR/xml-schema-1#cvc-datatype-valid.1.2.1?&decimal
> this message contains incorrect URI path, fragment & query values.
> it can also be argued that the URI should in the form
> [path][?query][#fragment]
> is this a time to re-factor the error message formatter so it is driven by:
> - spec name, version, etc.
> - rule violated
> - clause violated
> so a more accurate URI can be constructed?
> it might also be desirable to have a level of indirection between the spec
> name & version v. using a URI literal in the code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
