"Daniel John Debrunner (JIRA)" <[EMAIL PROTECTED]> writes: > Class.forName(JDBC_DERBY_DRIVER).newInstance();
The ".newInstance()" part can usually be dropped as well. The JDBC3 specification does not mention use of newInstance, I think. The Derby manuals use both versions; although mostly newInstance is omitted. I seem to remember I had to use newInstance to be able to re-load the driver in a test, though... In JDBC4, only a DriverManager.connect() call will be required (driver autoloading feature).
