tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Diogo Kollross" <>
Subject JULI ClassLoaderManager - weird behaviour with some class loaders
Date Mon, 07 Apr 2014 15:03:55 GMT

Reading the source of the readConfiguration(ClassLoader) method in ClassLoaderLogManager I
noticed that the input stream that is
used to load the properties file is not always set. It is only set when classloader is an
instance of URLClassLoader, and when it's
the system class loader. Right before the end of the method the root logger of the parent
class loader may be retrieved, but in this
case the properties file is not loaded as the stream was not set (with getResourceAsStream
for example).

Is this intentional? Is it expected that the class loader will always be a URLClassLoader
or the system class loader? Then why is
the root logger of the parent class loader searched whenever the input stream is not set?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message