'No suitable Driver' - Drivers don't get auto-loaded when only derbyrun.jar is
in the classpath with ibm 1.6 jvm.
-----------------------------------------------------------------------------------------------------------------
Key: DERBY-4872
URL: https://issues.apache.org/jira/browse/DERBY-4872
Project: Derby
Issue Type: Bug
Affects Versions: 10.7.1.0
Environment: Windows XP, with IBM 1.6 SR8 (and Sun/Oracle's
1.6.0_21-b07 for comparison).
Reporter: Myrna van Lunteren
Priority: Minor
With 1.6 jvms, doing DriverManager.getConnection() should autoload all drivers
in the classpath. If I understand this correctly, it's based on what's in the
manifest.mf, so it makes sense that you'd need to have jars, not just classes
in the classpath.
But, with ibm 1.6 jvm, if I have only derbyrun.jar in the classpath, I get the
message 'No suitable driver' with both the client, and the embedded driver.
However, if I add derby.jar to the classpath, the error goes away for the
embedded driver, and if I add derbyclient.jar, it goes away for the client
driver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
