[
https://issues.jboss.org/browse/TEIIDDES-291?page=com.atlassian.jira.plug...
]
John Doyle commented on TEIIDDES-291:
-------------------------------------
The WSDL to Relational Importer has changed it's implementation since this JIRA was
written, and the XML-Relational importer no longer exists. However this JIRA still
applies. I think in order to resolve this issue correctly (I'm not convinced that
this occurs often enough to warrant a fix), the importer would need to recognize the
choice and prompt the user to "pick one". Alternatively, the importer could
build view models for all the options, but the user would have to create some dynamic SQL
to figure out what views to execute depending upon what the XML actually is at runtime. I
can't imagine that actually working.
XML-Relational and WSDL-Relational importers do not understand the
substitutionGroup attribute of xsd:Element
-------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-291
URL:
https://issues.jboss.org/browse/TEIIDDES-291
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.1
Reporter: John Doyle
Assignee: John Doyle
Priority: Minor
Attachments: XSDTest7.java
See the issue tracker:
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...
Take a look at section 2.2.2.2 of the XSD spec.
http://www.w3.org/TR/xmlschema-1/
Or this nice example:
http://www.w3schools.com/Schema/schema_complex_subst.asp
As I read the spec, these substitution groups have no effect on the structure of the XML
defined by the XSD, only the names that allowed for a particular element in the XML.
We don't support this in the importer now. We would have to add functionality to
find the substitution groups and add additional XPaths so that the connector could either
/name or /navn in the xml document.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira