For automatic configuration it should be in the classpath. Put it in the shared classpath (i.e. tomcat/common/classes) if you want to configure every app. Put it in your app classpath (i.e. WEB-INF/classes) if you want to configure only your app. Where you put it affects where your log4j.jar should go (I think).
On 2/7/06, kameron cole <[EMAIL PROTECTED]> wrote: > I've searched wide for the answer of where to put the log4j.properties file > in a J2EE system. It's kind of sad to me that none of the articles begins > to address this really essential part of the set up. > > in one obscure post, someone said a "quick fix" was to put it in one of the > extension classloader folders for the various appservers. can't really be a > good thing, since it would affect everybody else's log4j. still, it does > work. > > so, it's not a problem that I don't understand the classpath - it's that > log4j looks somewhere, not everywhere, for a file called log4j.properties. > someone must know that exact place where the log4j designers intended to put > that file. > > thank you for any and all answers. > > -- > yours, > k. > > -- James Stauffer Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
