Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <239093211.1139340058072.JavaMail.jira@ajax.apache.org>
Date: Tue, 7 Feb 2006 20:20:58 +0100 (CET)
From: "Daniel John Debrunner (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (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=comments#action_12365472 ] 

Daniel John Debrunner commented on DERBY-930:
---------------------------------------------

In the policy file the patch has lines like:

+  // junitTests/jdbcapi/AutoloadTest.java
+  permission java.lang.RuntimePermission "getProtectionDomain";

but this permission is for generic code in DerbyJUnitTest, not just that specific test.

When the test runs with JDK 1.4 is it auto-loading the driver? I couldn't see any setting of jdbc.drivers so I'm unclear what would cause the driver to auto-load.

>From earlier comment:
> I disabled the security manager for AutoloadTest. The reasons for this are documented in AutoloadTest_app.properties: When running under our test harness from jar files under jdk1.6, system properties can't be read. This causes the drivers to silently fail to autoload. Note that when running under jdk1.6 from jar files outside our test harness, the drivers correctly autoload.

This is somewhat troubling, I don't understand what reading system properties has to do with the auto-loading of JDBC drivers by the java virtual machine. Can you maybe explain more why this fails for you, rather than just disabling the security manager. Disabling the security manager should not be a common option. I think it's as simple as you are not fetching the System property in a priv block.


> 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: bug930.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