Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of dkollross@empro.com.br
 designates 177.124.111.133 as permitted sender)
From: "Diogo Kollross" <dkollross@empro.com.br>
To: <dev@tomcat.apache.org>
Subject: JULI ClassLoaderManager - weird behaviour with some class loaders
Date: Mon, 7 Apr 2014 12:03:55 -0300
Message-ID: <015401cf5272$9858f5b0$c90ae110$@empro.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Ac9ScpgxnGbdZHfTT+akx4MH1pNB0Q==
Content-Language: pt-br

Hello,

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?

Regards,

Diogo


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org