3:59 p.m.
Barry LaFond created TEIIDDES-1486:
--------------------------------------
Summary: Create Data Source is broken with Teiid 8.x changes
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:29 p.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-1486:
-------------------------------------------
We can request these from the jboss subsystem. See
https://community.jboss.org/wiki/ConfigurationTreeForAJboss7Teiid8Server
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:47 p.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-1486:
----------------------------------------
Barry: on multiple JAR based driver files, the user needs to create JBoss module manually
and deploy it and define the data source definition inside the "standalone.xml"
or in "domain.xml" before that driver can be used. Whatever the name they give
in the xml file will be presented as the driver name in above list.
If you are *ONLY* looking for all the JDBC sources, you can issue a CLI command like
{code}
/subsystem=datasources:installed-drivers-list
{
"outcome" => "success",
"result" => [
{
"driver-name" => "teiid",
"deployment-name" => undefined,
"driver-module-name" => "org.jboss.teiid.client",
"module-slot" => "main",
"driver-datasource-class-name" => "",
"driver-xa-datasource-class-name" =>
"org.teiid.jdbc.TeiidDataSource",
"driver-class-name" => "org.teiid.jdbc.TeiidDriver",
"driver-major-version" => 8,
"driver-minor-version" => 2,
"jdbc-compliant" => false
},
{
"driver-name" => "h2",
"deployment-name" => undefined,
"driver-module-name" => "com.h2database.h2",
"module-slot" => "main",
"driver-datasource-class-name" => "",
"driver-xa-datasource-class-name" =>
"org.h2.jdbcx.JdbcDataSource",
"driver-class-name" => "org.h2.Driver",
"driver-major-version" => 1,
"driver-minor-version" => 3,
"jdbc-compliant" => true
}
{code}
here as you can see, you can get details on what are the driver names and driver-class
names. "driver-name" is what reported above through Teiid admin api. Since the
JDBC driver class name is not modifying between versions of jars may be you can have a
look-up mechanism based on "driver-class-name" and mapping back to the
"driver-name"
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:30 a.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1486:
----------------------------------------
Because we're using DataTools Connection Profiles, the profile properties are limited
to a simple "list of jars" for drivers of a connection profile. They do not
provide a single (aka delegate) "name" for the list of drivers.
I haven't seen a case yet where multiple drivers are required, but if it does, then
Designer could not programmaticaly extract the applicable "connector name" from
the CP. There will have to be user-intervention at this time which complicates the UI work
to fix this.
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:50 a.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-1486:
----------------------------------------
Can connection profile give you the name of the jdbc driver class name?
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1486:
----------------------------------------
Yes, I believe that is one of the required/derived properties when setting up a CP
driver.
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 p.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-1486:
----------------------------------------
then my suggestion is to use my comment from above to solve the issue.
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 a.m.
[
https://issues.jboss.org/browse/TEIIDDES-1486?page=com.atlassian.jira.plu...
]
Mark Drilling resolved TEIIDDES-1486.
-------------------------------------
Resolution: Done
Incorporated changes - https://github.com/Teiid-Designer/teiid-designer/pull/18
Create Data Source is broken with Teiid 8.x changes
---------------------------------------------------
Key: TEIIDDES-1486
URL: https://issues.jboss.org/browse/TEIIDDES-1486
Project: Teiid Designer
Issue Type: Bug
Components: Datatools Integration, Teiid Integration, VDB & Execution
Reporter: Barry LaFond
Assignee: Mark Drilling
Priority: Blocker
Fix For: 8.0
Teiid 8.x changes resulted in loosing our mapping of simple connection types to known
Teiid connection names. Hardcoded constants in DatasourceConnectionConstants were:
{code}
String JDBC = "connector-jdbc"; //$NON-NLS-1$
String SALESFORCE = "connector-salesforce"; //$NON-NLS-1$
String LDAP = "connector-ldap"; //$NON-NLS-1$
String FILE = "connector-file"; //$NON-NLS-1$
String JDBC_XA = "connector-jdbc-xa"; //$NON-NLS-1$
String WS = "connector-ws"; //$NON-NLS-1$
String UNKNOWN = "connector-unknown"; //$NON-NLS-1$
{code}
In 8.x, Teiid data source types are named mostly by their driver jars:
while in debug, my current list was:
* teiid-local
* teiid-connector-file.rar
* teiid
* teiid-connector-salesforce.rar
* teiid-connector-ldap.rar
* teiid-connector-ws.rar
* ojdbc6.jar
* h2
Also changed the type name of "connector-jdbc" in debug to
"ojdbc6.jar" and it successfully created a data source on teiid.
Need use driver jar from Connection Profile properties.
Note, that CP's are allowed to use "multiple driver jars??"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4266
days inactive
4278
days old
teiid-designer-issues@lists.jboss.org
7 comments
4 participants
participants (4)
-
Barry LaFond (JIRA) -
Mark Drilling (JIRA)
-
Paul Richardson (JIRA)
-
Ramesh Reddy (JIRA)