Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2008155139.1144694662444.JavaMail.jira@ajax>
Date: Mon, 10 Apr 2006 19:44:22 +0100 (BST)
From: "Rick Hillegas (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-930) Add support for autoloading of Derby
 client drivers
In-Reply-To: <1126289257.1139337537266.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-930?page=all ]

Rick Hillegas updated DERBY-930:
--------------------------------

    Attachment: bug930_rev2.diff

I have attached a revised patch for this feature: bug930_rev2.diff. This patch cannot be committed until mustang build 81 posts. That build should fix a jdk bug which short-circuits driver autoloading when running under a SecurityManager. This revised patch removes the need for the following permission when checking whether the test is running against the classtree or against jar files:

  permission java.lang.RuntimePermission "getProtectionDomain";

This patch touches the following files:

A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\AutoloadTest.java
M      java\testing\org\apache\derbyTesting\functionTests\suites\jdbc40.runall
M      java\testing\org\apache\derbyTesting\functionTests\util\TestConfiguration.java
M      java\testing\org\apache\derbyTesting\functionTests\util\BaseJDBCTestCase.java
M      build.xml

I will re-run the jdbc4 tests against this patch once mustang build 81 posts.

> Add support for autoloading of Derby client drivers
> ---------------------------------------------------
>
>          Key: DERBY-930
>          URL: http://issues.apache.org/jira/browse/DERBY-930
>      Project: Derby
>         Type: New Feature

>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>  Attachments: ClassloadingTest.jar, bug930.diff, bug930_problem.diff, bug930_problem2.diff, bug930_rev2.diff
>
> Write Derby's driver names into the correct spot in derby.jar and derbyclient.jar so that the 1.6 vm autoloads Derby drivers. Section 10.2.1 of the JDBC4 spec describes the details.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira