Hi Jacob, yes, I did think it odd that a web server/servlet container
(Tomcat) should pick up a properties file in one of its web apps! I now
think the more sane explanation is that I was hasty in my offhand reporting,
and that the "ton" of output I saw was from JSF, not Tomcat. That would
make a little more sense, because all JSF jars are in WEB-INF/lib of the
webapp. And, again, as mentioned, JSF was in the mix when I noticed the
same kind of copious output under Sun Web Server.
I should set root logger to DEBUG and look more closely at the output.
Regards,
--A
Log4j uses the thread context classloader to locate/load the property file,
but the thread wouldn't have been started from the webapp, so I don't see
how that would come into play here? Do you, somehow, have WEB-INF/classes
of your webapp in the system classpath or something? But if you use the
startup scripts, Tomcat eschews the system classpath. Hmmmmm.... In any
case, this is very odd.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
