db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers
Date Thu, 22 Feb 2007 19:19:10 GMT

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

Daniel John Debrunner commented on DERBY-930:

With this issue it seems that the changes made to auto-loading (the two stages) means that
the Existing Application Impact flag should be unchecked.

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

View raw message