Hi For getting the connection using DriverManager class, an instane of the driver is required in the registerDriver method. But Class.forName returns the Class object associated with the class or interface with the given string name, so you can even tell the driver to be used by your program using the property file.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
by calling the method Class.forName. This explicitly loads the driver class. loading the class causes an instance to be created and also calls DriverManager.registerDriver with that instance as the parameter, then it is in the DriverManager's list of drivers and available for creating a connection.
Once the Driver classes have been loaded and registered with the DriverManager class, they are available for establishing a connection with a database. When a request for a connection is made with a call to the DriverManager.getConnection method, the DriverManager tests each driver in turn to see if it can establish a connection.
It may sometimes be the case that more than one JDBC driver is capable of connecting to a given URL In such cases, the order in which the drivers are tested is significant because the DriverManager will use the first driver it finds that can successfully connect to the given URL.
First the DriverManager tries to use each driver in the order it was registered. (The drivers listed in jdbc.drivers are always registered first.) It will skip any drivers that are untrusted code unless they have been loaded from the same source as the code that is trying to open the connection.
Gravitation cannot be held responsible for people falling in love ~ Albert Einstein
Been there. Done that. Went back for more. But this time, I took this tiny ad with me: