Re: logging system initialization

2006-10-30 Thread Ed Griebel
...but note that unless you are dong something fancy, log4j doesn't need any separate initialization steps as long as the log4j config file is set up properly and in the classpath so log4j's static initializer can find it. One problem I have run into before is when there are two log4j.xml files i

Re: logging system initialization

2006-10-30 Thread Ping Yu
Ed, Right now commons-digester.jar is in the webapp's classpath, and so it is the jar file (management.jar) which includes my log file, but it still gets the log4j warning error message. log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.TldConfig). lo

Re: logging system initialization

2006-10-30 Thread Chris Pratt
If you need to initialize anything before the rest of the system gets a hold of it (like logging), use a javax.servlet.ServletContextListener and process the contextInitialized() event. It gets called before anything else in the context gets initialized. (*Chris*) On 10/30/06, Ed Griebel <[EMAI

Re: logging system initialization

2006-10-30 Thread Ed Griebel
For a WAR file you are going to deploy: create a log4j.properties or a log4j.xml file and get it into your warfile under WEB-INF/classes. The actual process of doing this differs if you are using Maven, an IDE deployer (e.g. JDeveloper or WSAD), or Ant to generate and deploy a WAR. For a webapp r

logging system initialization

2006-10-30 Thread Ping Yu
People in the list, I have my own log.java, and I would like to make a call to my own log definitions before initialize/using the digester (org.apache.commons.digester.Digester). However, I have no idea how to call my own log first. Any suggestions? Thank you very much! Right now, I