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] Closed: (DERBY-930) Add support for autoloading of Derby client drivers
Date Fri, 21 Jul 2006 19:17:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-930?page=all ]

Rick Hillegas closed DERBY-930.

    Resolution: Fixed
    Derby Info: [Existing Application Impact, Release Note Needed]  (was: [Release Note Needed,
Existing Application Impact])

Closing this issue because DERBY-1459 addresses the problem.

> Add support for autoloading of Derby client drivers
> ---------------------------------------------------
>                 Key: DERBY-930
>                 URL: http://issues.apache.org/jira/browse/DERBY-930
>             Project: Derby
>          Issue Type: New Feature
>          Components: Build tools, JDBC
>            Reporter: Rick Hillegas
>         Assigned To: Rick Hillegas
>             Fix For:
>         Attachments: autoloading_scenarios.html, bug930.diff, bug930_problem.diff, bug930_problem2.diff,
bug930_rev2.diff, bug930_rev3.diff, ClassloadingTest.jar
> 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


View raw message