[DERBY-503] Documentation should recommend using .newInstance() to instantiate JDBC driver

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.1.0
• Fix Version/s: 10.5.1.1
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Oyvind Bakksjo
• Created: 12/Aug/05 18:01
• Updated: 02/May/13 02:29
• Resolved: 27/Aug/08 20:23

Description

Using Class.forName("<driver name>").newInstance() is the recommended way to load and instantiate the JDBC driver, but the documentation does not contain the .newInstance() part.

Pointers:

http://db.apache.org/derby/docs/10.1/devguide/cdevdvlp40653.html
http://db.apache.org/derby/docs/10.1/ref/rrefjdbc32052.html

The EmbeddedDriver javadoc mentions it:

"The JDBC specification recommends the Class.ForName method without the .newInstance() method call, but adding the newInstance() guarantees that Derby will be booted on any Java Virtual Machine."

Issue Links

• is depended upon by: DERBY-2958 need to mention ClientDriver In Derby reference manual's java.sql.Driver interface section