You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/06/07 23:36:25 UTC

[jira] Created: (DERBY-2784) With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver

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.


[jira] Resolved: (DERBY-2784) With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel John Debrunner resolved DERBY-2784.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

AutoloadedDriver.acceptsURL() does not need the real driver booted to indicate which URLs it supports

    Sending        trunk/java/engine/org/apache/derby/jdbc/AutoloadedDriver.java
    Transmitting file data ...
    Committed revision 545329.

> 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
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>
> 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.


[jira] Updated: (DERBY-2784) With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver

Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel John Debrunner updated DERBY-2784:
-----------------------------------------

    Priority: Minor  (was: Major)
    Assignee: Daniel John Debrunner

Minor because an application might take the path to explicitly load the driver given that exception and explicitly loading the driver does no harm.

> 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
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>
> 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.