[JBoss JIRA] (TEIIDDES-2526) Import from SOAP wizard pops up multiple validation result messages
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2526?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-2526.
---------------------------------
Resolution: Done
Nulled out validation message after display to prevent it from popping up when selecting "Back" in the wizard. Fixed check for changed CP since it was comparing the same instance to itself. Saved off CP properties prior to editing and compare those with current CP property values after editing. This will force an edited CP to get reloaded after edit, which was not happening before. Also fixed missing message key for endpoint tooltip.
> Import from SOAP wizard pops up multiple validation result messages
> -------------------------------------------------------------------
>
> Key: TEIIDDES-2526
> URL: https://issues.jboss.org/browse/TEIIDDES-2526
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Web Services Support
> Affects Versions: 9.0.2
> Reporter: Andrej Šmigala
> Assignee: Ted Jones
> Fix For: 9.2, 9.0.3
>
>
> Clicking around the SOAP import wizard, the WSDL Validation Results message pops up several times, sometimes showing the wrong result (validation success when the connection profiles is in fact invalid).
> Also, when opening the wizard again after closing it, a validation error pops up.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2460.
------------------------------------
Resolution: Out of Date
Retesting resulted in the imported datatype is "integer".
Note that Designer was changed in 9.x to not allow selecting the "integer" datatype. So the use-case was changed to define both *int* and *string* typed columns.
On re-import (deployed) VDB, the imported type is "integer" which is Teiid's runtime type which is supported for legacy purposes. There is no way to tell what the original datatype from the original VDB because Teiid converts it via their JDBC metadata.
marking as Out Of Date
> JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2460
> URL: https://issues.jboss.org/browse/TEIIDDES-2460
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 9.2, 9.0.3
>
> Attachments: ErrorDialog.png
>
>
> When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised
> Version-Release number of selected component (if applicable):
> Actual results:
> Imported schema has changed integer data type to biginteger data type.
> Expected results:
> Imported schema will be identical to original schema.
> Additional info:
> Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2560) Although DV 6.0(Teiid 8.4.1) is selected as teiid instance on JBDS, TD 9.0.1 uses grant-all in vdb.xml
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2560?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2560.
------------------------------------
Resolution: Done
> Although DV 6.0(Teiid 8.4.1) is selected as teiid instance on JBDS, TD 9.0.1 uses grant-all in vdb.xml
> ------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2560
> URL: https://issues.jboss.org/browse/TEIIDDES-2560
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 9.0.1
> Environment: JBDS8.1 with TD 9.0.1.Final
> Reporter: hisao furuichi
> Assignee: Barry LaFond
> Fix For: 9.2, 9.0.3
>
>
> The version of Teiid engine in the selected Teiid instance will be displayed on the VDB editor(window for editing user role). So user expects if DV 6.0(Teiid 8.4.1) is selected as a teiid instance, all of modification to a VDB will be optimized for DV 6.0.(Teiid 8.4.1). However grant-all attribute which should not be used for Teiid 8.4.1 is used. (The issue is reported at TEIIDDES-2353)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2553) Changing parameter types in REST connection results in wrong URL
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2553?page=com.atlassian.jira.plu... ]
Ted Jones resolved TEIIDDES-2553.
---------------------------------
Resolution: Out of Date
The parameter type changing issue was resolved by https://issues.jboss.org/browse/TEIIDDES-2552 by adding the buttons to move parameters up/down to generate the desired URL. The delete issue was also fixed as part of that Jira.
The issue with the preview URL not updating is due to the known and expected behavior of the Combo box in SWT. Setting focus somewhere else will cause the correct events to fire to update the preview URL.
> Changing parameter types in REST connection results in wrong URL
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2553
> URL: https://issues.jboss.org/browse/TEIIDDES-2553
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 9.0.2 Beta2
> Reporter: Andrej Šmigala
> Assignee: Ted Jones
> Fix For: 9.2, 9.0.3
>
>
> Changing the type of a parameter in the REST connection profile causes the generated URL to be wrong. Also, the Preview URL is not updated after changing the type, only after some other action (testing connection, changing the default value etc).
> Furthermore, removing the paramters does not work if the type of the parameter has been changed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2581) SalesForce.com soap api 23
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2581?page=com.atlassian.jira.plu... ]
Steven Hawkins reassigned TEIIDDES-2581:
----------------------------------------
Assignee: (was: Steven Hawkins)
Changing to Designer as that is where the import is happening. Also with Teiid 8.10 the Opportunity table for v22 does not have a CreditCardNumber column, so this is not reproducible on the Teiid side.
> SalesForce.com soap api 23
> --------------------------
>
> Key: TEIIDDES-2581
> URL: https://issues.jboss.org/browse/TEIIDDES-2581
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
>
> When importing the definition of the Opportunity Object from SalesForce, the CreditCardNumber field always comes without a data type, it only shows error on the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2581) SalesForce.com soap api 23
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2581?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-3565 to TEIIDDES-2581:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2581 (was: TEIID-3565)
Affects Version/s: (was: 8.7.1)
Component/s: Import/Export
(was: Salesforce Connector)
> SalesForce.com soap api 23
> --------------------------
>
> Key: TEIIDDES-2581
> URL: https://issues.jboss.org/browse/TEIIDDES-2581
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA
> JBoss Data Virtualization 6.1.0.ER4
> Reporter: Jorge Herrera
> Assignee: Steven Hawkins
>
> When importing the definition of the Opportunity Object from SalesForce, the CreditCardNumber field always comes without a data type, it only shows error on the model.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months