[
https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1233:
------------------------------------------
Ted/Barry,
At least what I inferred initially was that this is an XML document model scenario, see
the attached vdb. If the user hand models the document, then the namespace settings are
not correctly conveyed in the index via the MappingDocumentFormatter expects an associated
schema. It would be best though if Debbie could confirm this assumption as the original
case was not entirely clear.
Teiid cannot handle child elements belonging to a different
namespace
---------------------------------------------------------------------
Key: TEIIDDES-1233
URL:
https://issues.jboss.org/browse/TEIIDDES-1233
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.6
Reporter: Debbie Steigner
Assignee: Ted Jones
Fix For: 7.7.1
Attachments: foo.zip
In the case where a web service is returning a response similar to the
following:
<ns1:searchMidbWSResponse ... >
< ns1:return>
< ns1:Site>
<ns2:PropOne>...</ ns2:PropOne>
< ns2:PropTwo>...</ ns2:PropTwo>
etc...
</ ns1:Site>
</ ns1:return>
</ ns1:searchMidbWSResponse>
Notice that all of the Site property elements belong to a different namespace
(alias=ns2) whereas the outer elements belong to the namespace with the ns1
alias. It looks like EDS cannot handle child elements belonging to a different
namespace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira