db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers
Date Tue, 07 Feb 2006 19:43:58 GMT
    [ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12365476 ] 

Rick Hillegas commented on DERBY-930:

Thanks for your quick review, Dan. Some responses follow:

1) I'll change the comments in the policy file to note that the code is generic to DerbyJUnitTest

2) I was simply testing the autoloading added by JDBC4. You are right that setting jdbc.drivers
under JDBC3 should cause autoloading too. I will add the AutoloadTest to the jdk1.4 suite
while setting jdbc.drivers appropriately.

3) I will investigate wrapping the property reader in a priv block to see if this fixes the
permissions problem. I may have to ask you for more advice here before I touch bottom.

> 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:
For more information on JIRA, see:

View raw message