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] Updated: (DERBY-930) Add support for autoloading of Derby client drivers
Date Thu, 09 Feb 2006 00:34:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-930?page=all ]

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

    Attachment: bug930_problem.diff

I have attached bug930_problem.diff, which demonstrates the problem I am having autoloading
Derby drivers under a SecurityManager. The problem case contains the following  files:

A      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\AutoloadDriver.java
A      autoloadscript
M      build.xml
A      autoload.policy

Once you have applied this patch to a clean client, you can reproduce the problem by invoking
the script from the directory above trunk:

trunk/autoloadscript


> 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, bug930_problem.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


Mime
View raw message