[JBoss JIRA] (TEIIDDES-2459) Enabling minimal support for as-yet unsupported Teiid versions
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2459?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2459:
-----------------------------------
Fix Version/s: 8.6.2 Beta1
8.6.2
> Enabling minimal support for as-yet unsupported Teiid versions
> --------------------------------------------------------------
>
> Key: TEIIDDES-2459
> URL: https://issues.jboss.org/browse/TEIIDDES-2459
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Teiid Integration
> Affects Versions: 9.0.2
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> Since there is only one teiid-client plugin which is responsible for all versions of teiid instance support, there is no longer any point in specifying versions that the plugin supports.
> Thus, update the plugin to establish levels of support for versions of Teiid, ie. no support, full support and works-but-no-support. This should allow versions of Teiid that have not yet been fully integrated and tested to be connected to by the client.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2452) The result of wsdl validation in SOAP web-service importer is not shown for a user
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2452?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2452:
-----------------------------------
Fix Version/s: 8.6.2 Beta1
8.6.2
> The result of wsdl validation in SOAP web-service importer is not shown for a user
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-2452
> URL: https://issues.jboss.org/browse/TEIIDDES-2452
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.6.1
> Environment: JBDS 7.1.1
> JBDSIS 7.1.0
> Windows 7
> Reporter: Filip Elias
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> Steps to reproduce:
> 1, File> Import > Web Service Source >> Source and View Mode (SOAP)
> 2, Select connection profile
> 3, Click Validate WSDL
> If the wsdl or URL is incorrect the TD will display error.
> However if the wsdl or URL is OK then the TD won't display any message about successful validation and the button became greyish.
> User should be informed that the validation finished successfully.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2405:
------------------------------------
Attachment: cassandra-ra.txt
> 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
> Fix For: 9.1, 9.0.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.11#6341)
11 years
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-2405.
-------------------------------------
Resolution: Done
DataSourceManager code in designer was incorrectly testing for resource adapter before setting the class-name property - which was not a necessary step. The managedconnectionfactory-class default value should alway be used.
Removed the unnecessary check and retest ok.
https://github.com/Teiid-Designer/teiid-designer/pull/441
Steps to retest
1) add the attached cassandra resource adapter to standalone.xml resource adapters section
2) In designer, launch the 'teiid connection importer'. On the first page of the wizard, click "New..." to create a new data source.
3) On the Create DataSource dialog - in Available Drivers list, click on 'cassandra' type.
4) For the cassandra DataSource properties, the 'class-name' property should have a value of 'org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory'.
(Prior to this fix, the class-name was not getting set)
> 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
> Fix For: 9.1, 9.0.2
>
>
> 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.11#6341)
11 years