[DERBY-930] Add support for autoloading of Derby client drivers

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.2.1.6
• Component/s: Build tools, JDBC
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 08/Feb/06 03:38
• Updated: 01/Jul/09 00:34
• Resolved: 22/Feb/07 19:46

Description

Write Derby's driver names into the correct spot in derby.jar and derbyclient.jar so that the 1.6 vm autoloads Derby drivers. Section 10.2.1 of the JDBC4 spec describes the details.

Issue Links

• is related to: DERBY-1429 Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly
• relates to: DERBY-1459 Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is made with another driver