Ok.

I've included the log4j.jar in my WEB-INF/lib directory and created a
log4j.xml file based on an example I found online (rather then a
log4j.properties file). The application deploys error free and executes -
however my log files are not created.

I can think of two reasons this could be happening:
1) Log4j is not creating the "log" directory, thus it can't create the log
file; or
2) I'm missing the piece to connect my application to log4j. In my code, I
create a variable using the following statement:

"protected static Log log = LogFactory.getLog(ControllerServlet.class);"

Now is that enough for commons-logging and log4j to create the log file they
need, or am I missing another piece somewhere?

Below is the log4j.xml properties file. I'm using a relative path to specify
a directory for the log files (i.e. "log/uwaf-event.log"). Given that I'm
using Tomcat 5.5 as my app server - where will it try to create my log
files? In my webapps/<myapp> folder, or in the <Catalina_home>/bin
directory?

Thanks,

Darren



-----Original Message-----
From: Dave Newton [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, June 13, 2006 2:18 PM
To: Struts Users Mailing List
Subject: Re: [newb question] Turning on DEBUG level logging

Darren Hall wrote:
> So essentially, I should download Log4J, include the jar in my classpath
and
> create a "Log4J.xml" file. Correct?
>   

Most people use the properties file, but the XML config gives you more
power. I've always handled XML config init programmatically; I don't
know if it works automagically.

Dave



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to