Thanks for the clarification. Some applications might be actually registering the driver themselves. What are the problems that this might cause (if the app calls DriverManager.registerDriver() explicitly)?
Regards,
Suavi
Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
Suavi Ali Demir wrote:
> After a shutdown=true, you should be able to connect to the same
> database again after doing a DriverManager.registerDriver(
> Class.forName(driverName).newInstance() )
No, that's not the correct way to start Derby or any other JDBC driver.
JDBC drivers are required to register themselves, applications should
not be registering drivers.
Simply loading the driver and creating an instance of it will start
Derby again.
Class.forName(driverName).newInstance();
Dan.
