[
https://jira.jboss.org/jira/browse/TEIID-683?page=com.atlassian.jira.plug...
]
Steven Hawkins updated TEIID-683:
---------------------------------
Workaround Description: Edit the connector binding contained in the VDB zip archive in
the ConfigurationInfo.def file and remove the ConnectorTypeClasspath entry or recreate the
connector binding under a Teiid Designer 6.1 version or later. (was: Rename the extension
jar connector-jdbc-6.2.0-SNAPSHOT.jar to connector-jdbc-6.0.0.jar)
We do not want users renaming extension jars to support invalid connector binding. I
updated the workaround to reflect this. I'm inclined to state that we don't want
to support connector bindings from 6.0 designer. They contain other hidden information
beyond just the connector type classpath that may have their default values change in
future versions.
Connector fails to start due to JDBC Connector ClassNotFound
Exception
----------------------------------------------------------------------
Key: TEIID-683
URL:
https://jira.jboss.org/jira/browse/TEIID-683
Project: Teiid
Issue Type: Bug
Components: Embedded
Affects Versions: 6.1.0, 6.2.0
Environment: Embedded 6.2 kit
Reporter: Van Halbert
Assignee: Steven Hawkins
Attachments: QT_ora11ds.vdb
Using a VDB that was created using 6.0 version. The connector type in the
Configuration.def in the vdb has the ConnectorTypeClasspath value points to
connector-jdbc-6.0.0.jar. The configuration.xml in the embedded kit has the
connectortype classpath set to:
extensionjar:connector_patch.jar;extensionjar:connector-jdbc-6.2.0-SNAPSHOT.jar. The
embedded extensions directory contains connector-jdbc-6.2.0-SNAPSHOT.jar. In order to
get the connector to start, the extension jar has to be renamed to
connector-jdbc-6.0.0.jar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira