[
https://issues.apache.org/jira/browse/DERBY-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036159#comment-13036159
]
Knut Anders Hatlen commented on DERBY-5239:
-------------------------------------------
The change looks fine to me too. The server code may now start using a
different instance of the driver than the one found returned by
DriverManager.getDriver(), but since all the methods of EmbeddedDriver end up
calling static methods in AutoloadedDriver anyway, I don't think that it would
cause any problems (like booting two engine instances in the same JVM).
> 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:
> svn-patch-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
