[teiid-issues] [JBoss JIRA] Commented: (TEIID-683) Connector fails to start due to JDBC Connector ClassNotFound Exception

[Steven Hawkins (JIRA)]

    [ https://jira.jboss.org/jira/browse/TEIID-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12472809#action_12472809 ] 

Steven Hawkins commented on TEIID-683:
--------------------------------------

Exactly - so changing the kit to conform to an invalid connector binding is not the right path. If that binding is recreated in 6.1 it will not contain any of the hidden entries or even non-modified default entries.

> 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