[
https://issues.jboss.org/browse/JBTIS-260?page=com.atlassian.jira.plugin....
]
Paul Richardson commented on JBTIS-260:
---------------------------------------
Updated Designer 8.3.x to a target platform of Integration-stack version 4.1.8.Final. This
now matches JBDS 7.1.1 org,eclipse.datatools.connectivity plugins. However, this does not
fix the problems.
Consistently trying to execute a vdb results in a three exceptions, one of which has the
following stacktrace:
{code}
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.internal.ManagedConnection.createConnection(ManagedConnection.java:166)
at
org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}
Looking at the source of this exception leads to the DriverValidator and this line:
{code}
boolean emptyJarListIsOK = this.mTemplate.getEmptyJarListIsOKFlag();
{code}
Clearly, mTemplate being null is generating the NullPointerException. This field is
directly extracted from the DriverInstance (Teiid driver instance) upon construction of
the validator so the teiid driver must have a null template. *Why??*
By opening the connection properties of the vdb's connection, the driver properties
section is blank with no actual JDBC driver selected. By choosing the 8.4.x driver from
the dropdown list, the teiid connection starts to work again and a query can be
successfully made. So, *why is the appropriate driver for the teiid version not
selected??*
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: Barry LaFond
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