[
https://issues.apache.org/jira/browse/WODEN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467952
]
John Kaputin commented on WODEN-126:
------------------------------------
The reason that the XMLElement might wrap an <xs:import> element defined
directly under <wsdl:type>, rather than an <xs:schema> element that it imports,
is that it is a namespace that is imported, not a schema document, and this may
be resolved to schema components in that namespace in some
implementation-specific way. As the objective of the getXMLElement() method is
to facilitate applications using their own schema processing techniques, then
it makes sense to just return the <xs:import> wrapped by XMLElement and let the
application use its own technique to resolve the import.
> Underlying <xs:schema> element should be accessible from API
> ------------------------------------------------------------
>
> Key: WODEN-126
> URL: https://issues.apache.org/jira/browse/WODEN-126
> Project: Woden
> Issue Type: Improvement
> Reporter: John Kaputin
> Assigned To: John Kaputin
> Fix For: M7
>
>
> Woden supports XML Schema datatypes via ws-commons XmlSchema, but Woden users
> may prefer to use other mechanisms for manipulating schema information. The
> API should allow the user to access the underlying <xs:schema> element
> 'wrapped' by the ImportedSchema or InlinedSchema object so they have the
> flexibility to choose other mechanisms. For example, in the DOM
> implementation the underlying schema element is an org.w3c.dom.Element
> object. To avoid API-dependencies on particular XML parsers or object models
> the org.apache.woden.XMLElement class should be used for this purpose, as
> this is an abstraction of DOM Element, OM Element, etc.
> The org.apache.woden.schema.Schema interface (supertype of ImportedSchema and
> InlinedSchema) requires two new methods:
> void setSchemaElement(XMLElement)
> XMLElement getSchemaElement()
--
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]
