Yes, it is probably the case Log4J is initialized earlier. We are
running Tapestry 5 in a Jetty server. Now the trick will be to find
out how and where to catch the initialization and have it take into
account our properties file.
Alex
Le 6 févr. 08 à 18:31, Andrus Adamchik a écrit :
If I
If I am not mistaken your conversion pattern "[%p] %c{1} %m%n" does
not match the output, so it is very likely that some other dependency
and/or container trigger Log4J initialization prior to your code being
executed.
Andrus
On Feb 6, 2008, at 11:57 AM, Alexander Lamb (dev) wrote:
Well
Well, I tried but didn't work.
Indeed, BEFORE loading a model (I have two models that I load
explicitly) I do:
public AppModule() {
System.out.println(" AppModule init...");
System.out.println("- LOG4J: " + getClass().getResource("/
log4j.properties"));
org
.apache.log
As a background to what Kevin just said, Cayenne itself no longer
attempts to configure Log4J (something it did prior to 3.0). Log4J is
optional and is expected to be configured by the user.
http://cayenne.apache.org/doc/guide-to-30-features.html
(search for "logging" on this page).
And
How are you bootstrapping your log4j configuration? I have something like
the following before creating a DC:
org.apache.log4j.PropertyConfigurator.configure(getClass().getResource("/log
4j.properties"));
--
Kevin
On 2/5/08 11:29 AM, "Alexander Lamb (dev)" <[EMAIL PROTECTED]> wrote:
> Hello
