[jbosstools-issues] [JBoss JIRA] (JBTIS-260) Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2

[Paul Richardson (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957318#comment-12957318 ] 

Paul Richardson commented on JBTIS-260:
---------------------------------------

Designer has for some time assumed a certain id for the Teiid Driver. When a JDBC connection is requested (either previewing or executing), the driver for the driver id is requested from eclipse's Driver Manager. If no driver can be found then Designer creates a new driver based on the connection properties provided during preview or VDB execution. This driver is pretty sparse in not even having a template and this is the problem.

Investigations (by [~lfabriko]) have dug up [this|https://github.com/eclipse/datatools.connectivity/commit/c7d5a3632e25fa2308e59bcf91f22f039ac40af9] change in the connectivity plugin. This has tightened up the JDBCConnection class to ensure that the driver selected for the JDBC connection is first validated using the Driver Validator. However, the driver validator assumes the driver should have a template and thereby throws the exception shown above where the template is null.

Designer should fix this by ensuring that one of the 3 teiid drivers provided are used for the JDBC connection as there should be no need to create a new one. This will bypass the problem with the created sparse driver and ensure that the correct driver is used for the JDBC query.
 
                
> Teiid designer server management tasks fail for JBDS 7.1.1.GA + JBDSIS 7.0.1.CR2
> --------------------------------------------------------------------------------
>
>                 Key: JBTIS-260
>                 URL: https://issues.jboss.org/browse/JBTIS-260
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: teiid
>         Environment: JBDS 7.1.1.GA, JBDSIS 7.0.1.CR2, server DV6 GA
>            Reporter: Lucie Fabrikova
>            Assignee: Paul Richardson
>            Priority: Blocker
>         Attachments: DriverValidator-1.2.11
>
>
> In teiid designer, start server latest DV6 GA and create new model project. Create some source model.
> - preview of data in table causes error with empty stack trace, development perspective is not opened
> - create and execute vdb: development perspective is opened, but vdb is not connected; trying to connect causes NPE: 
> java.lang.NullPointerException
> 	at org.eclipse.datatools.connectivity.drivers.DriverValidator.validateJarListFiles(DriverValidator.java:161)
> 	at org.eclipse.datatools.connectivity.drivers.DriverValidator.isValid(DriverValidator.java:92)
> 	at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getDriverDefinitionJarPaths(JDBCConnection.java:217)
> 	at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.getJdbcDriverJars(JDBCConnection.java:169)
> 	at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.<init>(JDBCConnection.java:67)
> 	at org.teiid.datatools.connectivity.TeiidJDBCConnection.<init>(TeiidJDBCConnection.java:31)
> 	at org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:21)
> 	at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> 	at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> 	at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:705)
> 	at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690)
> 	at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38)
> 	at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45)
> 	at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59)
> 	at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114)
> 	at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163)
> 	at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

--
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