classloader

Assume I have the following class: class Caller { public void createSomething() { new Something(); } } Would executing this line: static void main() { Class<?> clazz = Caller.class; } cause the JVM to load the class Something or is the class loading deferred until the method createSomething() is called? A class is loaded only when you require information about that class. public class SomethingCaller { public static Something something = null; // (1) does not cause class loading public static Class<?> somethingClass = Something.class; // (2) causes class loading public void doSomething() { new

As of Java-8, I know the hierarchy of the classloaders has been as follows:- Bootstrap classloader -> Extension classloader -> Application classloader What is the change in the hierarchy of classloaders in Java 9 and how does it works? The ClassLoader as revised in Java-9 states that: The Java run-time has the following built-in class loaders: Bootstrap class loader : The virtual machine's built-in class loader typically represented as null, and does not have a parent. Platform class loader : To allow for upgrading/overriding of modules defined to the platform class loader, and where upgraded

What does this message in Eclipse's logcat for Android mean? W/ActivityThread: ClassLoader.getResources: The class loader returned by Thread.getContextClassLoader() may fail for processes that host multiple applications. You should explicitly specify a context class loader. For example: Thread.setContextClassLoader(getClass().getClassLoader()); Unfortunately, there is no context given as to this warning, so I don't know what causes this problem and how I can resolve it. Background information The message means that Android has setup a dummy ClassLoader with Thread.currentThread()

I am using some third party code which when given a '-classpath' command line argument doesnt set the java.class.path, but instead just creates a classloader, adds all the urls for the items on the command line specified classpath to the classloader, and then sets it to be the context classloader. In a plugin class to this code that I have written, I get an instance of this classloader, and somehow need to use it to get back the underlying classpath, so that I can use it in an invocation of JavaCompiler.getTask(...) and compile some other code on the fly. However there doesn't seem to be

I have multiple web-apps running on an app server and each web-app WAR file contains a copy of the same jar file. Does this mean that a class in that jar file will be loaded multiple times in the JVM, once for each WAR file it exists in? Following on from that, if I have a static synchronized method in such a class, is it only synchronized among threads within the web-app it exists in but not synchronized against the same method in the same class in a different jar file in a different WAR file? (Hope the question makes sense, will clarify if necessary). If this is the case I presume the best