[
https://issues.apache.org/jira/browse/WODEN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467223
]
John Kaputin commented on WODEN-10:
-----------------------------------
r499639 provides the fix for this WSDL 2.0 testcase. At least, for the DOM
implementation. I'll apply the fix to the OM implementation too.
The solution suggested in XERCESJ-100 was to provide some behaviour in an
XMLEntityResolver registered with the DOM parser to resolve the fragid to a
schema element, serialize that schema element to a byte stream and put the byte
stream in the InputSource object passed to the DOM parser.
I took a similar approach for this fix, but instead used the
SchemaResolverAdapter class that Woden registers with XmlSchemaCollection
(effectively, the schema parser). This class and its subclass,
DOMSchemaResolverAdapter, now have behaviour that resolves the fragid to a
schema element, serializes this to a byte steam and passes this in an
InputSource to the XmlSchemaCollection.read method. When XmlSchema is invoked
by Woden to parse an inline schema and it encounters an xs:import inside the
inlined schema that contains a fragid in its schemaLocation, the
SchemaResolverAdapter.resolveEntity method gets invoked by XmlSchema which
triggers the new behaviour to resolve the fragid.
> 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.
-
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]
