[
https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu...
]
Steven Hawkins updated TEIIDDES-1233:
-------------------------------------
Assignee: (was: Steven Hawkins)
Document models can be created that have nested namespaces, and Teiid contains code to use
different namespace prefixes for nested elements. However at least for my simple test
case (see attached) the generated mapping document does not contain any namespaceURI
information for the elements - it only has the namespace declarations. It would appear
that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri
with elements at least for a simple hand made document model. I don't know if things
are different when starting with a schema.
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
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