Whenever i write code for database connection , i use to wonder why i have to load a jdbc driver with Class.forName(). why shouldn the api do this for us , coz its the common thing everyone does.

Finally JDBC 4.0 helped…

if JDBC 4.0 is used , we need not load the JDBC driver , since the api does this for us , provided the driver is in classpath.

and some more explanation about the new features of JDBC 4.0 is available here

i havent tried this api yet and so i have some queries ,

like ….

what if there are two or more jdbc drives in the classpath , which one will be loaded … and so on

will update more about this api , once i finish my experiments :)….