[DERBY-5239] Remove usages of DriverManager to obtain an Embedded Connection in Derby Server

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0, 10.8.1.2
• Fix Version/s: 10.8.2.2, 10.9.1.0
• Component/s: Network Server
• Urgency: Normal
• Assignee: Ed Costello
• Reporter: Ed Costello
• Created: 18/May/11 03:53
• Updated: 17/Jun/13 09:19
• Resolved: 23/May/11 12:25

Description

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.