db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6647) The ij.driver property is obsolete and need not be documented
Date Thu, 03 Jul 2014 20:36:33 GMT

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

Kim Haase updated DERBY-6647:

    Attachment: DERBY-6647.zip

Attaching DERBY-6647.diff, DERBY-6647.stat, and DERBY-6647.zip, with these changes:

D       src/tools/rtoolsijpropref41073.dita
M       src/tools/rtoolsdrvrnmeurl.dita
M       src/tools/rtoolsijcomref39042.dita
M       src/tools/derbytools.ditamap
M       src/tools/ttoolsij97656.dita

This patch removes the ij.driver topic and modifies 3 others, describing a current use for
the Driver command.

Please let me know if more changes are needed. 

> The ij.driver property is obsolete and need not be documented
> -------------------------------------------------------------
>                 Key: DERBY-6647
>                 URL: https://issues.apache.org/jira/browse/DERBY-6647
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6647.diff, DERBY-6647.stat, DERBY-6647.zip
> The ij.driver property is not useful any more and can be removed from the documentation.
According to Rick Hillegas, "The purpose of the ij.driver property is to tell ij to manually
load a driver class via Class.forName().newInstance(). That's the ancient way of loading drivers.
The modern way is to rely on driver autoloading."
> The Driver command may still be useful for reloading the driver after the Derby engine
has been shut down and the driver deregistered, so that can be kept.

This message was sent by Atlassian JIRA

View raw message