classloader

Okay, so say I have a class that looks like this : public class SignupServlet extends HttpServlet { private static final Logger SERVLET_LOGGER=COMPANYLog.open(SignupServlet.class); private static final ExceptionMessageHandler handler = new ExceptionMessageHandler(); private static final SignupServletObservableAgent signupObservableAgent = new SignupServletObservableAgent(null, SERVLET_LOGGER); } Can I count on the class loader to initialize those fields in order, such that I can rely on SERVLET_LOGGER to be instantiated before signupObservableAgent? Laurence Gonsalves Yes, they are initialized

So far, the examples I have seen for custom ClassLoaders involve subclassing the URLClassLoader, and using that specific instance to load classes in resources. I have tried in vain to look for alternative methods to replace the SystemClassLoader, so that my ClassLoader can be consulted for classes not located in the classpath. I tried Thread.currentThread().setContextClassLoader , but it doesn't seem to work. Is it even possible? Though this is an old question, there is indeed a way to replace the system ClassLoader. You might get more than you bargained for, however, with reflection. Field

Below are 2 code snippets The first one uses ClassLoader class to load a specified class ClassLoader cls = ClassLoader.getSystemClassLoader(); Class someClass = cls.loadClass("TargetClass"); The second one uses Class.forName() to load a specified class Class cls = Class.forName("TargetClass"); What is the difference between the above said approaches. Which one serves for which purpose? Quick answer (without code samples) With the explicit ClassLoader cls = <a ClassLoader>; approach you have the flexibility of loading the class from a ClassLoader that is not your default ClassLoader. In your