[
https://issues.apache.org/jira/browse/DERBY-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001637#comment-13001637
]
Rick Hillegas commented on DERBY-5043:
--------------------------------------
Thanks, Kim. These changes look good. One small point in rrefattribderegister:
Both the second and third bullets are instances of autoloading. Both of these
patterns trigger the autoloading logic in DriverManager. The only difference
between them is how DriverManager comes up with the list of drivers to
autoload. The second bullet describes the original autoloading which was
introduced by JDK 1.4. The third bullet describes an additional form of
autoloading which was introduced by Java 6.
> Document the new url attribute deregister to keep the AutoloadedDriver
> registers in DriverManager
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-5043
> URL: https://issues.apache.org/jira/browse/DERBY-5043
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.7.1.1
> Reporter: Lily Wei
> Assignee: Kim Haase
> Labels: derby_triage10_8
> Fix For: 10.8.0.0
>
> Attachments: DERBY-5043.diff, DERBY-5043.stat, DERBY-5043.zip,
> Repro2905.java
>
>
> With DERBY-2905, we have a new connection url attribute - deregister. After a
> shutdown of the embedded driver, the AutoloadedDriver is unregistered from
> the DriverManager. Users who wish to keep the AutoloadedDriver can set the
> deregister attribute on the connection url to false. It is only valid with
> shutdown=true. And, the default behavior with shutdown=true is
> deregister=true.
> For example:
> 'shutdown=true;deregister=true" (It is okay not to specify deregister=true)
> 'shutdown=true;deregister=false"
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
