[
https://issues.jboss.org/browse/TEIIDDES-882?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-882:
---------------------------------------
The WSDL to Relational importer contains a portion of these steps.
Key addition here is inclusion of sample request/response documents that can be used by
the view procedure generator (UI) where the user can select columns from the sample XML
documents to solidify/define the SQL statement
Examples would be:
Generated SQL example for create:
CREATE VIRTUAL PROCEDUREBEGIN
SELECT XMLELEMENT(
NAME CapitalCity,
XMLNAMESPACES(DEFAULT
'http://www.oorsprong.org/websamples.countryinfo'),
XMLELEMENT(NAME sCountryISOCode,
COUNTRYINFOSERVICEXML.CAPITALCITY.CREATE_CAPITALCITY.sCountryISOCode))
AS xml_out;END
Generated SQL example for extract:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT t.* FROM XMLTABLE(
XMLNAMESPACES(DEFAULT 'http://www.oorsprong.org/websamples.countryinfo'),
'/CapitalCityResponse'
PASSING
COUNTRYINFOSERVICEXML.CAPITALCITY.EXTRACT_CAPITALCITYRESPONSE.xml_in
COLUMNS CapitalCityResult string)
AS t;
END
Create new SOAP service connection profile.
-------------------------------------------
Key: TEIIDDES-882
URL:
https://issues.jboss.org/browse/TEIIDDES-882
Project: Teiid Designer
Issue Type: Sub-task
Components: Import/Export
Affects Versions: 7.1, 7.2, 7.3
Reporter: John Doyle
Assignee: Ted Jones
Fix For: 7.7.1, 8.0
Attachments: SOAP Connection Profile Wizard.bmml, SOAP Connection Profile
Wizard.bmml, SOAP Connection Profile Wizard.png
For the WSDL into Relational Model Importer we take advantage of the DTP provided Web
Service Data Source connection profile. We really only did this because of time
constraints. That profile has attributes that don't make sense for Teiid Designer and
are ignored by Designer. We really need our own dedicated connection profile that
provides the correct interface to the user and enables us to satisfy existing issues we
cannot solve with the DTP profile.
--
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