[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2326:
-----------------------------------
Fix Version/s: 9.2.2
(was: 9.2.1)
> REST/SOAP importers - Re use of the connection profile after restart
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2326
> URL: https://issues.jboss.org/browse/TEIIDDES-2326
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.2.2
>
> Attachments: nomodel.png
>
>
> Often times, as user I start the import of WSDL based or REST (with new one, or old with file and URL selection) service and go through the wizard, something does not work right. So, I typically remove the models generated, and then try the import process again. However, next time when I select the same connection profile I created before, I very seldom get same results. If I restarted the Designer for any reason, the previously created connection profile for sure does not work.
> It seems to me that, designer stores a temp XML/JSON file from where it starts processing, during the restart that gets deleted and import process instead of sending another request for the results document it fails with arbitrary error. There is no way to recover form it. IMO, REST and SOAP needs to be treated differently from XML File type sources and issue the query to get response document, not store it anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2545) Importing REST service gives a string instead of a boolean to a procedural parameter
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2545?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-2545.
---------------------------------
Resolution: Cannot Reproduce Bug
I have not been able to reproduce.. marking as Not Reproducible.
> Importing REST service gives a string instead of a boolean to a procedural parameter
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2545
> URL: https://issues.jboss.org/browse/TEIIDDES-2545
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.1
> Environment: Windows 7
> Reporter: Daan Creemers
> Assignee: Ted Jones
> Fix For: 9.2.1
>
>
> After importing a REST service an error is given in the Transformation Editor: TEIID30145 Unable to convert procedural parameter SourceModel.invokeHttp.stream of type string to expected type boolean
> This is because there are quotes around TRUE for the stream parameter and these should be removed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2687) Dynamic VDB generation - Default value for string column problem (DDL)
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2687?page=com.atlassian.jira.plu... ]
Mark Drilling edited comment on TEIIDDES-2687 at 12/21/15 4:58 PM:
-------------------------------------------------------------------
Here is a summary of current Designer behavior. I set the default value in designer, exported dynamic vdb, then re-imported the dynamic vdb.
||Case||Designer Default value||Exported DDL||Import back into Designer||
|1|defaultValue|col1 string(4000) DEFAULT defaultValue|defaultValue|
|2|"defaultValue"|col1 string(4000) DEFAULT "defaultValue"|"defaultValue"|
|3|"default Value"|col1 string(4000) DEFAULT "default Value"|"default Value"|
|4|default Value|col1 string(4000) DEFAULT default Value|FAIL - fails re-import|
|5|'defaultValue'|col1 string(4000) DEFAULT 'defaultValue'|defaultValue - removes ticks|
|6|'default Value'|col1 string(4000) DEFAULT 'default Value'|default Value - removes ticks|
was (Author: mdrillin):
Here is a summary of current Designer behavior. I set the default value in designer, exported dynamic vdb, then re-imported the dynamic vdb.
||Case||Designer Default value||Exported DDL||Import back into Designer||
|1|defaultValue|col1 string(4000) DEFAULT defaultValue|OK - defaultValue|
|2|"defaultValue"|col1 string(4000) DEFAULT "defaultValue"|OK - "defaultValue"|
|3|"default Value"|col1 string(4000) DEFAULT "default Value"|OK - "default Value"|
|4|default Value|col1 string(4000) DEFAULT default Value|FAIL - fails re-import|
> Dynamic VDB generation - Default value for string column problem (DDL)
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2687
> URL: https://issues.jboss.org/browse/TEIIDDES-2687
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Patch Release, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 9.2.1
>
>
> I have a model with table that has String column with default value "Stock".
> DDL generated by TD for dynamic VDB looks like this:
> {quote}
> ...
> TYPE string(15) DEFAULT ('Stock') OPTIONS(NAMEINSOURCE '"TYPE"', NATIVE_TYPE 'VARCHAR2', UPDATABLE 'FALSE'),
> ...
> {quote}
> *DEFAULT ('Stock')* is not correct, it should be: *DEFAULT '("Stock")'*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2687) Dynamic VDB generation - Default value for string column problem (DDL)
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2687?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-2687:
-----------------------------------------
Here is a summary of current Designer behavior. I set the default value in designer, exported dynamic vdb, then re-imported the dynamic vdb.
||Case||Designer Default value||Exported DDL||Import back into Designer||
|1|defaultValue|col1 string(4000) DEFAULT defaultValue|OK - defaultValue|
|2|"defaultValue"|col1 string(4000) DEFAULT "defaultValue"|OK - "defaultValue"|
|3|"default Value"|col1 string(4000) DEFAULT "default Value"|OK - "default Value"|
|4|default Value|col1 string(4000) DEFAULT default Value|FAIL - fails re-import|
> Dynamic VDB generation - Default value for string column problem (DDL)
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2687
> URL: https://issues.jboss.org/browse/TEIIDDES-2687
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Patch Release, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 9.2.1
>
>
> I have a model with table that has String column with default value "Stock".
> DDL generated by TD for dynamic VDB looks like this:
> {quote}
> ...
> TYPE string(15) DEFAULT ('Stock') OPTIONS(NAMEINSOURCE '"TYPE"', NATIVE_TYPE 'VARCHAR2', UPDATABLE 'FALSE'),
> ...
> {quote}
> *DEFAULT ('Stock')* is not correct, it should be: *DEFAULT '("Stock")'*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-2748.
---------------------------------
Resolution: Done
Added logic to account for null schema type and simple types in WSDL parts.
> ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2748
> URL: https://issues.jboss.org/browse/TEIIDDES-2748
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.3, 9.2
> Reporter: Debbie Steigner
> Assignee: Ted Jones
> Fix For: 9.2.1
>
>
> Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected.
> On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked.
> On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation>
> The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-2748:
--------------------------------
Fix Version/s: 9.2.1
(was: 9.0.4)
> ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2748
> URL: https://issues.jboss.org/browse/TEIIDDES-2748
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.3, 9.2
> Reporter: Debbie Steigner
> Assignee: Ted Jones
> Fix For: 9.2.1
>
>
> Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected.
> On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked.
> On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation>
> The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months