[ 
https://issues.apache.org/jira/browse/WODEN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466201
 ] 

John Kaputin commented on WODEN-10:
-----------------------------------

error message from XmlSchema has changed to:
Woden[Error],0:0,WSDL521,Could not parse an inline schema in the WSDL at URL 
"file:/C:/workspace/woden/woden/downloads/w3c/documents/good/SchemaId-1G/schemaIds.wsdl".,java.lang.RuntimeException:org.apache.ws.commons.schema.XmlSchemaException:
 An imported schema was announced to have the namespace 
http://greath.example.com/2004/schemas/reservationItems, but has the namespace 
http://greath.example.com/2004/services/retrieveDetails

In attempting to resolve the schema import, XmlSchema retrieves the root WSDL 
document containing the two inlined schemas, but assumes this document is a 
schema document with a TNS that matches the imported namespace - hence 
mismatched namespace error message.

> Test Case Failure: test-suite/documents/good/SchemaId-1G/schemaIds.wsdl
> -----------------------------------------------------------------------
>
>                 Key: WODEN-10
>                 URL: https://issues.apache.org/jira/browse/WODEN-10
>             Project: Woden
>          Issue Type: Bug
>          Components: Parser
>            Reporter: Arthur Ryman
>         Assigned To: John Kaputin
>            Priority: Critical
>             Fix For: M7
>
>
> This test is failing because a schema location uses a fragment identifier to 
> refer to a schema located in the same document. The schema parser incorrectly 
> assumes the URL points to a schema document, i.e. it ignores the fragment 
> identifier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to