[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2405:
----------------------------------------
commited to 8.6.x: https://github.com/Teiid-Designer/teiid-designer/commit/971a77a8ff0f74fe0...
9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/d46c35b22937625f5...
> 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, 8.6.2 Beta1, 9.0.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.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2405:
-----------------------------------
Fix Version/s: 8.6.2 Beta1
9.0.2 Beta1
8.6.2
> 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, 8.6.2 Beta1, 9.0.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.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2422:
-----------------------------------
Fix Version/s: 8.6.2 Beta1
8.6.2
> XSD model created in wrong folder when creating Web service model from WSDL
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2422
> URL: https://issues.jboss.org/browse/TEIIDDES-2422
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder.
> Expected result:
> The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder.
> Actual result:
> The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ]
Barry LaFond reopened TEIIDDES-2422:
------------------------------------
Assignee: Barry LaFond (was: Ted Jones)
re-opened to merge into 8.6.x
> XSD model created in wrong folder when creating Web service model from WSDL
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2422
> URL: https://issues.jboss.org/browse/TEIIDDES-2422
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.1, 9.0.2 Beta1, 9.0.2
>
>
> When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder.
> Expected result:
> The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder.
> Actual result:
> The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2439:
-----------------------------------
Fix Version/s: 8.6.2 Beta1
8.6.2
> Import from JSON error not helpful
> ----------------------------------
>
> Key: TEIIDDES-2439
> URL: https://issues.jboss.org/browse/TEIIDDES-2439
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months
[JBoss JIRA] (TEIIDDES-2439) Import from JSON error not helpful
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2439?page=com.atlassian.jira.plu... ]
Barry LaFond reopened TEIIDDES-2439:
------------------------------------
Assignee: Barry LaFond (was: Ted Jones)
re-opened til merged and tested in 8.6.x
> Import from JSON error not helpful
> ----------------------------------
>
> Key: TEIIDDES-2439
> URL: https://issues.jboss.org/browse/TEIIDDES-2439
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Fix For: 9.1, 9.0.2 Beta1, 9.0.2
>
>
> When importing from a json document, occasionally people are using docs with multiple expressions. The exception shown seems like xml parsing is being used. It should be clearer or offer an option of which expression to use.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 7 months