Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) Workaround: Workaround Exists Workaround Description: Users can create the procedures manually. project_key: SOA 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.
Link: Added: This issue Cloned to SOA-2803
Link: Removed: This issue Cloned to SOA-2803
Link: Added: This issue Cloned to SOA-2805
Patch/fix is now available from TEIIDDES-781 that introduces an option in the New Model > Relational model wizard to "Create File Translator procecdures". This simplifies the use-case and prevents user-error. Recommend applying patch and getting in to JBDS CR2.
on the trunk version I'm seeing invoke/invokeHttp with result parameter modeled as IN rather than as a result. invokeHttp contenttype should also be an OUT parameter.
also all parameters to invoke/invokeHttp should be nullable.
A patch for shawkins comments. Fear that this may have missed the boat. User can modify these operations manually as a workaround.
Attachment: Added: SOA-2786.patch.txt
Adding remaining bug to Teiid Designer queue.
Link: Added: This issue is related to TEIIDDES-869
Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: The procedures created by the Teiid Designer's New Model Wizard for the Web Service Translator models the 'result' and 'contentype' parameters as IN parameters. They should be modeled as OUT parameters. Also, all the parameters should be modeled as 'nullable'. The user can edit these properties on the procedures to correct the model.
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Writer: Added: Darrin Release Notes Text: Removed: The procedures created by the Teiid Designer's New Model Wizard for the Web Service Translator models the 'result' and 'contentype' parameters as IN parameters. They should be modeled as OUT parameters. Also, all the parameters should be modeled as 'nullable'. The user can edit these properties on the procedures to correct the model. Added: https://issues.jboss.org/browse/TEIIDDES-869 The procedures created by the JBoss Developer Studio Teiid Designer's "New Model Wizard" for the Web Service Translator models the 'result' and 'contentype' parameters as IN parameters. They should be modeled as OUT parameters. Also, all the parameters should be modeled as 'nullable'. As a workaround you must edit these properties on the procedures to correct the model.