[JBoss JIRA] (TEIIDDES-2402) Web Service Input Variables not shown after opening the model
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2402?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2402.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Web Service Input Variables not shown after opening the model
> -------------------------------------------------------------
>
> Key: TEIIDDES-2402
> URL: https://issues.jboss.org/browse/TEIIDDES-2402
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors, Web Services Support
> Affects Versions: 8.3.4, 9.0.1
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: WsVariablesProject.zip
>
>
> When opening a Web Service model editor by double-clicking the model in the model explorer, the Input Variables section is empty, even when there are variable declarations in the procedure SQL.
> Trying to add the variables using the Add or Remove variables button results in multiple identical declarations in the procedure SQL.
> When opening the model editor by double clicking the child interface or operation, the input variables are shown as expected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2395) Add shortcut to Find Model Object in the Model Explorer Tab
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2395?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2395:
--------------------------------------
Reopening to set label
> Add shortcut to Find Model Object in the Model Explorer Tab
> -----------------------------------------------------------
>
> Key: TEIIDDES-2395
> URL: https://issues.jboss.org/browse/TEIIDDES-2395
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Editors
> Affects Versions: 8.6
> Reporter: Joao Viragine
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: find-model-object-in-explorer-toolbar.png
>
>
> It would be nice if we had a shortcut to "Find Model Object" in the Model Explorer Tab.
> It isn't productive to need to go to Menu/Search/Teiid Designer/Find Model Object every time we need to serach for a Model Object
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2405:
--------------------------------------
Reopening to set label
> Teiid Importer *MUST* not require class-name property working with Teiid Sources
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2405
> URL: https://issues.jboss.org/browse/TEIIDDES-2405
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Priority: Critical
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: cassandra-ra.txt
>
>
> When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source
> {code}
> {"managedconnectionfactory-class" => {
> "type" => STRING,
> "display" => "managedconnectionfactory-class",
> "read-only" => "true",
> "advanced" => "true",
> "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory"
> }},
> {code}
> That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2405.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Teiid Importer *MUST* not require class-name property working with Teiid Sources
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2405
> URL: https://issues.jboss.org/browse/TEIIDDES-2405
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.6
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Priority: Critical
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: cassandra-ra.txt
>
>
> When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source
> {code}
> {"managedconnectionfactory-class" => {
> "type" => STRING,
> "display" => "managedconnectionfactory-class",
> "read-only" => "true",
> "advanced" => "true",
> "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory"
> }},
> {code}
> That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2418) Converting all source symbol data types not reflected in Type Resolver
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2418?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2418:
--------------------------------------
Reopening to set label
> Converting all source symbol data types not reflected in Type Resolver
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2418
> URL: https://issues.jboss.org/browse/TEIIDDES-2418
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs, Transformations
> Affects Versions: 9.0.2
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Priority: Minor
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: TyperesolverProject.zip
>
>
> When using the Type Resolver, clicking the Convert all source SQL symbol datatypes does not show the changed expression in the Source SQL Symbol column. Other than that, it works as expected, i.e. the type conflict message goes away, and after clicking OK, the Reconciller actually contains the correct CONVERT statements.
> However, clicking the left arrows for each column correctly changes the Source SQL Symbol.
> Clicking Change all target column datatypes shows similar behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2418) Converting all source symbol data types not reflected in Type Resolver
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2418?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2418.
------------------------------------
Labels: verified_jbdsis-8.0.2.CR3 (was: )
Resolution: Done
> Converting all source symbol data types not reflected in Type Resolver
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2418
> URL: https://issues.jboss.org/browse/TEIIDDES-2418
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs, Transformations
> Affects Versions: 9.0.2
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Priority: Minor
> Labels: verified_jbdsis-8.0.2.CR3
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: TyperesolverProject.zip
>
>
> When using the Type Resolver, clicking the Convert all source SQL symbol datatypes does not show the changed expression in the Source SQL Symbol column. Other than that, it works as expected, i.e. the type conflict message goes away, and after clicking OK, the Reconciller actually contains the correct CONVERT statements.
> However, clicking the left arrows for each column correctly changes the Source SQL Symbol.
> Clicking Change all target column datatypes shows similar behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years