Class loaders are hierarchical. Classes are introduced into the JVM as they are referenced by name in a class that is already running in the JVM. So how is the very first class loaded? The very first class is specially loaded with the help of static main() method declared in your class. All the subsequently loaded classes are loaded by the classes, which are already loaded and running. A class loader creates a namespace. All JVMs include at least one class loader that is embedded within the JVM called the primordial (or bootstrap) class loader. Now let’s look at non-primordial class loaders. The JVM has hooks in it to allow user defined class loaders to be used in place of primordial class loader. Let us look at the class loaders created by the JVM.
Bootstrap : JDK internal classes, java.* packages.
Extensions : jar files from JDK extensions directory
System : classes from system classpath.
Bootstrap : JDK internal classes, java.* packages.
Extensions : jar files from JDK extensions directory
System : classes from system classpath.
Classes loaded by Bootstrap class loader have no visibility into classes loaded by its descendants (i.e Extensions and Systems class loaders).
The classes loaded by system class loader have visibility into classes loaded by its parents (i.e Extensions and Bootstrap class loaders).
If there were any sibling class loaders they cannot see classes loaded by each other. They can only see the classes loaded by their parent class loader.
The classes loaded by system class loader have visibility into classes loaded by its parents (i.e Extensions and Bootstrap class loaders).
If there were any sibling class loaders they cannot see classes loaded by each other. They can only see the classes loaded by their parent class loader.
Class loaders are hierarchical and use a delegation model when loading a class. Class loaders request their parent to load the class first before attempting to load it themselves. When a class loader loads a class, the child class loaders in the hierarchy will never reload the class again. Hence uniqueness is maintained. Classes loaded by a child class loader have visibility into classes loaded by its parents up the hierarchy but the reverse is not true.Two objects loaded by different class loaders are never equal even if they carry the same values, which mean a class is uniquely identified in the context of the associated class loader.
Dynamic class loading :
Dynamic loading is a technique for programmatically invoking the functions of a class loader at run time.
Class.forName (String className); //static method which returns a Class
Dynamic class loading :
Dynamic loading is a technique for programmatically invoking the functions of a class loader at run time.
Class.forName (String className); //static method which returns a Class
static method returns the class object associated with the class name. The string className can be supplied dynamically at run time. Unlike the static loading, the dynamic loading will decide whether to load the class House at runtime based on a properties file and/or other runtime conditions. Once the class is dynamically loaded the following method returns aninstance of the loaded class. It’s just like creating a class object with no arguments.
class.newInstance (); //A non-static method, which creates an instance of a class (i.e. creates an object).
House myHouse = null ;
//myClassName should be read from a properties file or Constants interface.
String myClassName = "com.hiren.House" ;
Class houseClass = Class.forName(myClassName) ;
myHouse = (House) houseClass.newInstance();
myHouse.setArea(5000);
0 comments:
Post a Comment