db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-930) Add support for autoloading of Derby client drivers
Date Sun, 25 Jun 2006 12:56:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-930?page=all ]

Kathey Marsden updated DERBY-930:
---------------------------------

    Attachment: autoloading_scenarios.html

The attached document autoloading_scenarios.html has three scenarios that need to be considered
for our autoloading implementation. Scenario's #1 and #3 have regressions with our current
implementation.  Scenario #2 will regress if we move processing of derby.drda.startNetworkServer
to connection time.





> 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

>   Components: Build tools, JDBC
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>      Fix For: 10.2.0.0
>  Attachments: ClassloadingTest.jar, autoloading_scenarios.html, bug930.diff, bug930_problem.diff,
bug930_problem2.diff, bug930_rev2.diff, bug930_rev3.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