Class RootLoader

  • All Implemented Interfaces:
    Closeable, AutoCloseable

    public class RootLoader
    extends URLClassLoader
    This ClassLoader should be used as root of class loaders. Any RootLoader does have it's own classpath. When searching for a class or resource this classpath will be used. Parent Classloaders are ignored first. If a class or resource can't be found in the classpath of the RootLoader, then parent is checked.

    Note: this is very against the normal behavior of classloaders. Normal is to first check parent and then look in the resources you gave this classloader.

    It's possible to add urls to the classpath at runtime through addURL(URL).

    Why using RootLoader? If you have to load classes with multiple classloaders and a classloader does know a class which depends on a class only a child of this loader does know, then you won't be able to load the class. To load the class the child is not allowed to redirect it's search for the class to the parent first. That way the child can load the class. If the child does not have all classes to do this, this fails of course.

    For example:

           parentLoader   (has classpath: a.jar;c.jar)
           childLoader    (has classpath: a.jar;b.jar;c.jar)
    class C (from c.jar) extends B (from b.jar) childLoader.find("C")
     --> parentLoader does know C.class, try to load it
     --> to load C.class it has to load B.class
     --> parentLoader is unable to find B.class in a.jar or c.jar
     --> NoClassDefFoundException!
    if childLoader had tried to load the class by itself, there would be no problem. Changing childLoader to be a RootLoader instance will solve that problem.