[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace
by Steven Hawkins (JIRA)
[ 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
13 years, 11 months
[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ]
Ted Jones edited comment on TEIIDDES-1233 at 5/8/12 10:36 PM:
--------------------------------------------------------------
We can definitely handle this using the WSDL to Source importer, however Steve is talking about document models which is a different animal, so I'm not sure what the actual use case is here. Are we generating web service models and not handling the response correctly, or is this using SQL/XML? Debbie, do you have that information?
was (Author: tejones):
We can definitely handle this using the WSDL to Source importer, however Steve is talking about document models which is a different animal. so I'm not sure what the actual use case is here. Are we generating web service models and not handling the response correctly, or is this using SQL/XML? Debbie, do you have that information?
> 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
13 years, 11 months
[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ]
Ted Jones commented on TEIIDDES-1233:
-------------------------------------
We can definitely handle this using the WSDL to Source importer, however Steve is talking about document models which is a different animal. so I'm not sure what the actual use case is here. Are we generating web service models and not handling the response correctly, or is this using SQL/XML? Debbie, do you have that information?
> 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
13 years, 11 months
[JBoss JIRA] (TEIIDDES-280) Update Count metadata property is not avaialble on the Web Service procedure
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-280?page=com.atlassian.jira.plug... ]
Barry LaFond commented on TEIIDDES-280:
---------------------------------------
A) XML Service model is retired so only fix here is to add the "Update Count" property to Web Service Operations
B) Mechanism to extend the Web Services model is via the new MED (Model Extension Definition) framework
So we'll need to:
1) Create a built-in MED maybe called "Web Services Built-in"
- Add ONE extended property on an Operation with display name "Update Count"
- ALLOWABLE VALUES : AUTO, MULTIPLE, ONE, ZERO
2) Have to wire this MED up so it's applied any time a Web Services model is created
3) Maybe create a Validation "warning" stating that "Web Services Model does not reflect built-in extended properties. Select WS Model and choose Modeling > Manage Model Extension Definitions to apply built-in extensions"
See Dan Florian for details. We already have built-in MEDs for Salesforce and basic "relational" model properties, so there are some examples to work from.
> Update Count metadata property is not avaialble on the Web Service procedure
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-280
> URL: https://issues.jboss.org/browse/TEIIDDES-280
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.1
> Reporter: Ramesh Reddy
> Assignee: Paul Richardson
> Fix For: 7.7.1
>
>
> "Update Count" metadata is not available on the Web Service procedure, this is only available on the virtual procedures. This data is used at run time to determine if procedure is "readonly", or does "single" or "multiple" updates to the underlaying databases. If this property not available then by default it is assumed that "multiple" updates and subject to the transactional restrictions in the server and dqp.
> Per SteveH, this property must be on any kind of procedure, may that be virtual, web and xml service.
--
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
13 years, 12 months