You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2007/02/22 20:48:05 UTC

[jira] Closed: (DERBY-930) Add support for autoloading of Derby client drivers

     [ https://issues.apache.org/jira/browse/DERBY-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas closed DERBY-930.
-------------------------------

    Resolution: Fixed

> Add support for autoloading of Derby client drivers
> ---------------------------------------------------
>
>                 Key: DERBY-930
>                 URL: https://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: 10.2.1.6
>
>         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.
-
You can reply to this email to add a comment to the issue online.