db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2784) With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver
Date Thu, 07 Jun 2007 21:36:25 GMT
With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException
No suitable driver
----------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2784
                 URL: https://issues.apache.org/jira/browse/DERBY-2784
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.2.2.0, 10.3.0.0
            Reporter: Daniel John Debrunner


The auto-load driver (org.apache.derby.jdbc.AutoloadedDriver) is loaded by the DriverManager
correctly (when running with jars in JDK 6) and fetching connections works without loading
the driver.

But prior to getting a connection seeing if a driver is available using DriverManager.getProtocol("jdbc:derby:")
incorrectly leads one to believe that no driver has been loaded.

Can see this running the junit test with jars and JDK6

org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest

(This test can be run directly and is part of the ant targt test running)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message