
Baeldung Pro comes with both absolutely No-Ads as well as finally with Dark Mode, for a clean learning experience:
Once the early-adopter seats are all used, the price will go up and stay at $33/year.
Last updated: January 26, 2025
A class loader is an object that is responsible for loading classes. Further, class loaders load Java classes dynamically to the JVM (Java Virtual Machine) during runtime. They’re also part of the JRE (Java Runtime Environment). Therefore, the JVM doesn’t need to know about the underlying files or file systems to run Java programs thanks to class loaders.
Furthermore, the JVM doesn’t load these Java classes into memory all at once, but rather when an application requires them. This is where class loaders come into the picture. They’re responsible for loading classes into memory.
In this tutorial, we’ll talk about different types of built-in class loaders and how they work. Then we’ll introduce our custom implementation.
Further reading:
Understanding Memory Leaks in Java
Learn what memory leaks are in Java, how to recognize them at runtime, what causes them, and strategies for preventing them.
ClassNotFoundException vs NoClassDefFoundError
Learn about the differences between ClassNotFoundException and NoClassDefFoundError.
A class loader has two main functions:
At the outset, class loaders don’t create objects for array classes. Instead, the Java runtime creates them automatically as required. Therefore, when we use Class#getClassLoader() to find the class loader for an array class, it returns the class loader for its element type. Accordingly, an array class has no class loader if the element type is a primitive data type.
The Java run-time supports three built-in class loaders:
Let’s start by learning how we can load different classes using various class loaders:
public void printClassLoaders() throws ClassNotFoundException {
System.out.println("Platform Classloader:"
+ ClassLoader.getPlatformClassLoader());
System.out.println("System Classloader:"
+ ClassLoader.getSystemClassLoader());
System.out.println("Classloader of this class:"
+ PrintClassLoader.class.getClassLoader());
System.out.println("Classloader of DriverManager:"
+ DriverManager.class.getClassLoader());
System.out.println("Classloader of ArrayList:"
+ ArrayList.class.getClassLoader());
}
When executed, the above method prints:
Platform Classloader:jdk.internal.loader.ClassLoaders$PlatformClassLoader@5674cd4d
System Classloader:jdk.internal.loader.ClassLoaders$AppClassLoader@33909752
Classloader of this class:jdk.internal.loader.ClassLoaders$AppClassLoader@33909752
Classloader of DriverManager:jdk.internal.loader.ClassLoaders$PlatformClassLoader@5674cd4d
Classloader of ArrayList:null
As we can see, there are three different class loaders here: bootstrap (displayed as null), platform, and system.
The system class loader loads the class that contains the example method. Let’s remember that the system class loader loads our files in the classpath.
Next, the platform class loader loads the DriverManager class.
Finally, the bootstrap class loader loads the ArrayList class. A bootstrap or primordial class loader is the parent of all the others; however, it doesn’t have a parent.
However, we can see that for the ArrayList, it displays null in the output. This is because the bootstrap class loader is written in native code, not Java, so it doesn’t show up as a Java class. As a result, the behavior of the bootstrap class loader will differ across JVMs.
Now, let’s discuss each of these class loaders in more detail.
An instance of java.lang.ClassLoader loads Java classes. However, class loaders are classes themselves. So the question is, who loads the java.lang.ClassLoader itself? This is where the bootstrap or primordial class loader comes into play. It’s mainly responsible for loading JDK internal classes, typically rt.jar and other core libraries located in the $JAVA_HOME/jre/lib directory. Additionally, the Bootstrap class loader serves as the parent of all the other ClassLoader instances.
This bootstrap class loader is part of the core JVM and is written in native code, as pointed out in the above example. Different platforms might have different implementations of this particular class loader.
The platform class loader is a child of the bootstrap class loader and takes care of loading the standard core Java classes so that they’re available to all applications running on the platform.
The system or application class loader, on the other hand, takes care of loading all the application-level classes into the JVM. It loads files found in the classpath environment variable, -classpath, or -cp command line option. It’s also a child of the platform class loader.
Class loaders are part of the Java Runtime Environment. When the JVM requests a class, the class loader tries to locate the class and load the class definition into the runtime using the fully qualified class name. The java.lang.ClassLoader.loadClass(String name, boolean resolve) method is responsible for loading the class definition into runtime using its binary name. This method is an overloaded method; it has a variant java.lang.ClassLoader.loadClass(String name) with different parameters. It performs an ordered search:
As a result of the ordered search, if it doesn’t find the class and additionally we have set the resolve flag to true, it calls the resolveClass(Class) method on the resulting binary Class object.
As a result of the ordered search, if the class is not found, it throws java.lang.ClassNotFoundException.
Now, let’s examine three important features of class loaders.
The delegation model means that the ClassLoader class delegates the search for a class or resource to its parent class loader before it tries to find the class or resource itself. The delegation model is hierarchical by default. The ClassLoader class supports concurrent loading of classes; therefore, it is parallel capable. Class loader implementations can register themselves at initialization time if they are to be parallel capable.
Class loaders follow the delegation model, where on being requested to find a class or resource, a ClassLoader instance will delegate the search of the class or resource to the parent class loader.
Let’s say we have a request to load an application class into the JVM. The system class loader first delegates the loading of that class to its parent platform class loader, which in turn delegates it to the bootstrap class loader.
Only if the bootstrap and then the platform class loader are unsuccessful in loading the class, does the system class loader try to load the class itself.
As a consequence of the delegation model, it’s easy to ensure unique classes, as we always try to delegate upwards.
If the parent class loader isn’t able to find the class, only then will the current instance attempt to do so itself.
In addition, child class loaders are visible to classes loaded by their parent class loaders.
For instance, classes loaded by the system class loader have visibility into classes loaded by the platform and bootstrap class loaders, but not vice-versa.
To illustrate this, if Class A is loaded by the application class loader, and class B is loaded by the platform class loader, then both A and B classes are visible as far as other classes loaded by the application class loader are concerned.
Class B, however, is the only class visible to other classes loaded by the platform class loader.
The built-in class loader is sufficient for most cases where the files are already in the file system.
However, in scenarios where we need to load classes out of the local hard drive or a network, we may need to make use of custom class loaders.
In this section, we’ll cover some other use cases for custom class loaders and demonstrate how to create one.
Custom class loaders are helpful for more than just loading the class during runtime. A few use cases might include:
Below are more concrete examples where custom class loaders might come in handy.
Browsers, for instance, use a custom class loader to load executable content from a website. A browser can load applets from different web pages using separate class loaders. The applet viewer, which is used to run applets, contains a ClassLoader that accesses a website on a remote server instead of looking in the local file system.
It then loads the raw bytecode files via HTTP, and turns them into classes inside the JVM. Even if these applets have the same name, they’re considered different components if loaded by different class loaders.
Now that we understand why custom class loaders are relevant, let’s implement a subclass of ClassLoader to extend and summarise the functionality of how the JVM loads classes.
For illustration purposes, let’s say we need to load classes from a file using a custom class loader.
We need to extend the ClassLoader class and override the findClass() method:
public class CustomClassLoader extends ClassLoader {
@Override
public Class findClass(String name) throws ClassNotFoundException {
byte[] b = loadClassFromFile(name);
return defineClass(name, b, 0, b.length);
}
private byte[] loadClassFromFile(String fileName) {
InputStream inputStream = getClass().getClassLoader().getResourceAsStream(
fileName.replace('.', File.separatorChar) + ".class");
byte[] buffer;
ByteArrayOutputStream byteStream = new ByteArrayOutputStream();
int nextValue = 0;
try {
while ( (nextValue = inputStream.read()) != -1 ) {
byteStream.write(nextValue);
}
} catch (IOException e) {
e.printStackTrace();
}
buffer = byteStream.toByteArray();
return buffer;
}
}
In the above example, we defined a custom class loader that extends the default class loader and loads a byte array from the specified file.
Let’s discuss a few essential methods from the java.lang.ClassLoader class to get a clearer picture of how it works.
This method is responsible for loading the class given a name parameter. The name parameter refers to the fully qualified class name:
public Class<?> loadClass(String name, boolean resolve) throws ClassNotFoundException {
The Java Virtual Machine invokes the loadClass() method to resolve class references, setting resolve to true. However, it isn’t always necessary to resolve a class. If we only need to determine if the class exists or not, then we set the resolve parameter to false.
This method serves as an entry point for the class loader.
The default implementation of the method searches for classes in an order, already discussed.
This method is responsible for the conversion of an array of bytes into an instance of a class. Before we use the class, we need to resolve it:
protected final Class<?> defineClass(
String name, byte[] b, int off, int len) throws ClassFormatError
If the data doesn’t contain a valid class, it throws a ClassFormatError.
Also, we can’t override this method, since it’s marked as final.
This method finds the class with the fully qualified name as a parameter. We need to override this method in custom class loader implementations that follow the delegation model for loading classes:
protected Class<?> findClass(
String name) throws ClassNotFoundException
In addition, loadClass() invokes this method if the parent class loader can’t find the requested class.
The default implementation throws a ClassNotFoundException if no parent of the class loader finds the class.
This method returns the parent class loader for delegation:
public final ClassLoader getParent()
Some implementations, like the one seen before in Section 4, use null to represent the bootstrap class loader.
This method tries to find a resource with the given name:
public URL getResource(String name)
It’ll first be delegated to the parent class loader for the resource. If the parent is null, the path of the class loader built into the virtual machine is searched.
If that fails, then the method will invoke findResource(String) to find the resource. The resource name specified as an input can be relative or absolute to the classpath.
It returns a URL object for reading the resource, or null if the resource can’t be found or the invoker doesn’t have adequate privileges to return the resource.
It’s important to note that Java loads resources from the classpath.
Finally, resource loading in Java is considered location-independent, as it doesn’t matter where the code is running as long as the environment is set to find the resources.
In general, context class loaders provide an alternative method to the class-loading delegation scheme introduced in J2SE.
As we learned before, classloaders in a JVM follow a hierarchical model, such that every class loader has a single parent except for the bootstrap class loader.
However, sometimes when JVM core classes need to dynamically load classes or resources provided by application developers, we might encounter a problem.
For example, in JNDI, the core functionality is implemented by the bootstrap classes in rt.jar. But these JNDI classes may load JNDI providers implemented by independent vendors (deployed in the application classpath). This scenario calls for the bootstrap class loader (parent class loader) to load a class visible to the application loader (child class loader).
J2SE delegation doesn’t work here, and to get around this problem, we need to find alternative ways of class loading. This can be achieved using thread context loaders.
The java.lang.Thread class has a method, getContextClassLoader(), that returns the ContextClassLoader for the particular thread. The ContextClassLoader is provided by the creator of the thread when loading resources and classes. As of Java SE 9, threads in the fork/join common pool always return the system class loader as their thread context class loader.
Class loaders are essential to execute a Java program. In this article, we provided a good introduction to them.
We discussed the different types of class loaders, namely Bootstrap, Platform, and System class loaders. Bootstrap serves as a parent for all of them and is responsible for loading the JDK internal classes. Platform and system, on the other hand, load classes from the Java platform and classpath, respectively.
We also learned how class loaders work and examined some features, such as delegation, visibility, and uniqueness. Then we briefly explained how to create a custom class loader. Finally, we provided an introduction to Context class loaders.