I think Derby recommends using .newInstance() to load JDBC
drivers... In fact, it is required if you plan to shutdown and reboot
databases on the same thread/VM for Derby. Take a look at the javadoc
I'm trying to load the embedded derby driver, like this:
As Rajesh pointed out, the problem is most likely the CLASSPATH. If you
still have problems, please send the complete exception, including
stack trace, as this helps to figure out the problem.
By the way, you don't need the '.newInstance()' part - simply loading
the driver class will set up the Derby system.