[
https://issues.apache.org/jira/browse/WODEN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495990
]
Sriram Rao commented on WODEN-3:
--------------------------------
As described in the relevant JIRA, I have modified testAssertionSchema0016
method to accept a QName instead of a namespaceURI. Within the method, I get
the NameSpaceURI and the localpart from the QName supplied. The reportError
will then use both the namespace and the localpart to log an error.
The error message has been modified to
"Schema-0016 = The component ''{1}'' refers to the XML Schema namespace
''{0}''. But this namespace is not available. In order to reference components
from a XML Schema namespace the namespace must be imported or defined inline."
with the {1} referring to the local part and {0} referring to the namespace.
I have also modified the 2 calls to this testAssertionSchema0016 method to send
QName instead of the namespaceURI.
This has not been tested this against any WSDL or a JUnit test case. I have
attached the modified Class WSDLDocumentValidator and the Messages.properties
files with this email.
> Add the component name to the Schema-0016 assertion method
> ----------------------------------------------------------
>
> Key: WODEN-3
> URL: https://issues.apache.org/jira/browse/WODEN-3
> Project: Woden
> Issue Type: Improvement
> Components: Validation
> Reporter: John Kaputin
> Assigned To: John Kaputin
> Fix For: M8
>
>
> The message for Schema-0016 assertion just reports the namespace URI in
> error. It might be more useful to report the name of the schema component as
> well. This could be achieved by specifying two message parameters (local
> name and namespace URI) and changing the testAssertionSchema0016 method in
> the validator to accept a QName argument rather than a namespace string.
> The message could then be formatted with the element or type's local name as
> well as its namespace URI.
--
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]
