[
https://issues.apache.org/jira/browse/WODEN-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464270
]
John Kaputin commented on WODEN-123:
------------------------------------
Here's the discussion [1] from the WSDL 2.0 mailing list:
[1] http://lists.w3.org/Archives/Public/www-ws-desc/2007Jan/0078.html
The problem is that Woden currently attempts to filter out the schemas that are
*referenceable* by the WSDL 2.0 document (i.e. they are inlined or imported
directly within the wsdl:types element) and uses only those schemas to create
the ElementDeclarations and TypeDefinitions in the Component model. However,
*referenceability* is a document-centric concept that cannot be applied to the
Component model because we can't tell in the Component model which documents
particular WSDL or Schema components originated from (so we can't really say
that an ElementDeclaration or TypeDefinition is referenceable by the WSDL
components....we'd have to say by *which* WSDL components).
The correct approach is to extract the global elements and types from ALL
schemas accessible within the document model, regardless of whether their
namespaces are *referenceable*, and add them to the Component model as
ElementDeclarations and TypeDefinitions. ALL schemas include not only those
inlined or imported directly within a wsdl:types element but also any schema
trees imported by those schemas. And they include the schemas from any
wsdl:imported or wsdl:included schemas as well.
If a component model was changed so that a WSDL component referred to an
element or type that was not referenceable by it in the underlying infoset,
then if the component model is serialized or converted back to the element
model, an xs:import of the schema namespace should be added to the relevant
description's wsdl:types element to make those schema components referenceable
by that document. However, we can leave this functionality until we deal with
WSDL updates and editing in general (current focus up to M7 has been on
reading/parsing only).
> Component model should contain ALL schema elements and types
> ------------------------------------------------------------
>
> Key: WODEN-123
> URL: https://issues.apache.org/jira/browse/WODEN-123
> Project: Woden
> Issue Type: Bug
> Components: Parser
> Reporter: John Kaputin
> Assigned To: John Kaputin
> Fix For: M7
>
>
> As discussed via the WSDL 2.0 mailing list [1], the component model should
> contain the global element declarations and type definitions for ALL schemas
> accessible within the WSDL tree, not just those schemas inlined or imported
> directly within the wsdl:types elements. This includes any schemas nested
> within other schemas via xs:import, xs:include or xs:redefines.
> This change will fix WODEN-101 and WODEN-102 which capture WSDL 2.0 testcase
> failures for SparqlQuery-1G and SparqlQuerySimplified-1G respectively.
--
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]
