db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Costello (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5239) Remove usages of DriverManager to obtain an Embedded Connection in Derby Server
Date Wed, 18 May 2011 03:55:47 GMT

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

Ed Costello updated DERBY-5239:
-------------------------------

    Attachment: 0001-Remove-Driver-Manager-Usage-from-Network-Server.patch

Attached is a patch replacing the two usages in Network Server with direct usage of the embedded
driver.

> Remove usages of DriverManager to obtain an Embedded Connection in Derby Server
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-5239
>                 URL: https://issues.apache.org/jira/browse/DERBY-5239
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server
>    Affects Versions: 10.6.1.0, 10.8.1.2
>            Reporter: Ed Costello
>         Attachments: 0001-Remove-Driver-Manager-Usage-from-Network-Server.patch
>
>
> The Derby Network Server appears to look up the Derby Embedded Driver from the {{java.sql.DriverManager}}
in a couple of places in order to get the connection to the actual database.
> This means the network server cannot operate in environments where for whatever reason
it is not OK to access the embedded driver from the DriverManager. Just in general this behavior
is unexpected as it should be possible to directly load the embedded driver.
> I've observed this issue in 10.6.1.0 and checked that the relevant usages are unchanged
in trunk.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message