-
Bug
-
Resolution: Done
-
Critical
-
7.1.1, 7.2
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
Workaround Exists
-
If a user models a SOAP service defined by a WSDL using the WSDL to Relational Model importer, the importer creates the invoke() physical procedure for the user. The execute procedure is required to execute the translator/connector.
If the service is not defined by a WSDL (ie. REST service, XML RPC service, ...), or is File based, then the user currently has to go through the error prone process of creating the physical models that define the procedures for the File and WS translators. Since the declaration of these procedures is static and known, JBDS/Teiid Designer should create the models for the user.
For the File Translator we should define getFiles, getTextFiles, and saveFile.
For the WS Translator we should define invoke and invokeHttp.