Sagar Rohankar wrote:
Put those driver jar file on classpath.
This is certainly not a classpath issue, you would get a ClassNotFoundException otherwise, not a SQLException with the message "No suitable driver". You will get this exception when the driver isn't loaded at all, or the JDBC URL is plain wrong.
Balu Sadhasivam wrote:
if your intended driver is not registered to DriverManager.
Right, when you say
When the method getConnection is called, the DriverManager will attempt to locate a suitable driver from amongst those loaded at initialization and those loaded explicitly using the same classloader as the current applet or application.(using Class.forName())