Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 63885 invoked from network); 7 Jun 2007 21:55:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jun 2007 21:55:47 -0000 Received: (qmail 14193 invoked by uid 500); 7 Jun 2007 21:55:51 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 13968 invoked by uid 500); 7 Jun 2007 21:55:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 13947 invoked by uid 99); 7 Jun 2007 21:55:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2007 14:55:50 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2007 14:55:46 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D7FAE714208 for ; Thu, 7 Jun 2007 14:55:25 -0700 (PDT) Message-ID: <8568766.1181253325872.JavaMail.jira@brutus> Date: Thu, 7 Jun 2007 14:55:25 -0700 (PDT) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-2784) With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver In-Reply-To: <30111664.1181252185906.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on 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.