[
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