db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-5043) Document the new url attribute deregister to keep the AutoloadedDriver registers in DriverManager
Date Tue, 01 Mar 2011 19:44:42 GMT

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

Rick Hillegas updated DERBY-5043:
---------------------------------

    Urgency: Blocker  (was: Urgent)

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

        

Mime
View raw message