Additionally you can put log4j.properties in its own jar and put it in
$tomcat/lib.
That's the default for Tomcat 6+, but formally the location for shared
classpath entries is defined in the property common.loader in
$tomcat/conf/catalina.properties. So e.g. to re-establish the older
Thanks for your help. I included the properties file in a separate jar.
From: toriv...@arrive.no
To: users@wicket.apache.org
Date: Thu, 29 Mar 2012 08:38:57 +0200
Subject: RE: log4j.properties
Additionally you can put log4j.properties in its own jar and put it in
$tomcat/lib
This is a log4j issue, not Wicket. However, if memory serves, you can set
a system property before starting Tomcat. Something like:
-Dlog4j.configuration=name.and.location.of.your.log4j.properties.file
A log4j forum is probably the best place to query the current best
practice on this.
On Wed, Mar 28, 2012 at 10:17 PM, Richard W. Adams rwada...@up.com wrote:
This is a log4j issue, not Wicket. However, if memory serves, you can set
a system property before starting Tomcat. Something like:
-Dlog4j.configuration=name.and.location.of.your.log4j properties.file
This is the
