Description of problem: Creation of connection profile generates error Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start the DV6 CR1 server (with modeshape-*.properties set up) 2. in Database Development perspective, create new connection profile: - connection profile type: ModeShape - use driver from DV6 CR1: jboss-eap-6.1/dataVirtualization/jdbc/modeshape-jdbc-3.3.6.GA-redhat-3.jar - host: localhost, port: 8080, username: admin, password: admin, repository: dv 3. click Finish in Modeshape Profile Wizard Actual results: After clicking on Finish: Could not connect to New ModeShape(7). Error creating SQL Model Connection connection to New ModeShape(7). (Error: org/modeshape/jdbc/LocalJcrDriver) org/modeshape/jdbc/LocalJcrDriver Error creating JDBC Connection connection to New ModeShape(7). (Error: org/modeshape/jdbc/LocalJcrDriver) org/modeshape/jdbc/LocalJcrDriver In teiid designer problems log: java.lang.NoClassDefFoundError: org/modeshape/jdbc/LocalJcrDriver at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:627) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.teiid.designer.datatools.profiles.modeshape.ModeShapeJDBCConnection.createConnection(ModeShapeJDBCConnection.java:43) at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105) at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54) at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81) at org.teiid.designer.datatools.profiles.modeshape.ModeShapeJDBCConnectionFactory.createConnection(ModeShapeJDBCConnectionFactory.java:16) 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) Caused by: java.lang.ClassNotFoundException: org.modeshape.jdbc.LocalJcrDriver at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:627) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 22 more Expected results: Additional info:
The modeshape-jdbc-3.3.6.GA-redhat-3.jar that is produced by the CR1 installer and is located post-install in %DV_HOME%/jboss-eap-6.1/dataVirtualization/jdbc is incomplete because it contains only the files from the modeshape-jdbc module (a.k.a the remote driver). This depends (build-wise) on the the local driver module: modeshape-jdbc-local and a number of other ModeShape modules. I don't know what the intent of the modeshape-jdbc-3.3.6.GA-redhat-3.jar is, but it is incorrectly packaged. If the desired effect is to have a standalone (isolated) JDBC driver, the correct jar should be the modeshape-client-3.3.6.GA.jar, produced during the assembly phase by the modeshape-client module.
Horia Chiorean <hchiorea> updated the status of jira MODE-2128 to Closed
Commit af4797eb066fb620819850f89c9444583a0efdd1 to ip (6.0.0-fsw branch): BZ-1047927. The JDBC jar is modeshape-client*jar, not modeshape-jdbc*jar, so add that to the jdbc directory.
I assume this does not need to be documented as a known issue in Release Notes - setting to requires_doc_text- accordingly.
Verified in DV6 CR2 + JBDS 7.1.0.GA + JBDSIS 7.0.0.CR2
Verified in JBDSIS-7.0.0.GA-GA + DV 6.0.0.GA.