Because Log4j, by default, looks for config files in the default package.
Furthermore, because of Tomcat's child-first classloading behavior, if you
place log4j.properties in the default package of the webapp (WEB-INF/classes)
it won't bother looking in the parent classloader since it will ha
Hi
Could I trouble you to explain further why putting the application
log4j.properties in WEB-INF/classes, as opposed to WEB-INF/classes/properties,
would prevent the webapp classloader from seeing the tomcat's log4j.properties?
Gerald
> On 11 Jul, 2014, at 11:27 pm, "Jacob Kjome" wrote:
>
