hi!
I am still not clear as to where I need to write this class or method.
Will it not suffice to give the entries in the web.xml file itself.
This is the first time I am dealing with these, so please help.
What I have done till now is to get the static logger instance in the class
and then put
Hi!
I managed to get it working.
I wrote a Servlet and gave the entry in the web.xml file and in my file
called the logging file
I could not use the following though
env-entry
descriptionLog4j resource file name/description
env-entry-namelog4j/resource/env-entry-name
Jacob,
We use log4j 1.2.8 and we include the jar file right in out WEB-INF/lib directory of
our application. The log4j.properties file then lives inside the WEB-INF/classes
directory. This works well for us on IBM's WAS 4.x.
I've never seen anyone recommend having log4j at the container level,
Yup, that should work just fine. If you want to be able to modify the config
info while the app is running (e.g. turn on debugging in production without
reloading the app), here's another approach.
Create a directory and place it on the app server's classpath. For WLS
(depending on how you do
that we're going to have to work around :-(
Thanks,
Jacob
-Original Message-
From: Chappell, Simon P [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 11:31 AM
To: Struts Users Mailing List
Subject: RE: [OT] RE: log4j integration
Jacob,
We use log4j 1.2.8 and we include the jar
to put log4j in the server classpath to overcome the issue. This has not
been a problem under WAS 4.x
Simon
-Original Message-
From: Hookom, Jacob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 11:33 AM
To: Struts Users Mailing List
Subject: RE: [OT] RE: log4j integration
6 matches
Mail list logo
