-----Original Message----- From: Shapira, Yoav [mailto:Yoav...@mpi.com] Sent: Friday, June 11, 2004 12:59 PM To: Log4J Users List Subject: RE: Separate log file per servlet

Hi,

In my example, I set additivity to false for all the appenders, because I didn't know what was in the rest of his configuration file. It's better to over-isolate than get multiple copies of logging statements IMHO, but it's certainly not a requirement, and certainly more details need to be known in order to establish if that's a good approach for this scenario.

As for configuring log4j: do it once, in a ServletContextListener's contextInitialized method, not from a servlet.

As for the shared class using whatever appender its calling class is using: ack, that's a bit of a pain. Logging Domains would help here, but that's log4j 1.3 ;) You can also do this fairly nicely with some Aspects (as in AOP Aspects). You could pass the name of the calling class, the calling class itself, or the Logger object itself, to all methods in the shared class. That's simple and would work, though it's a bit ugly. You could figure out the calling class name using stack trace tricks, but that's costly from a performance perspective. I don't know what I'd pick in this scenario, but then again I wouldn't be in this scenario to start with because I really dislike the "every component [or class, or whatever] goes into its own log destination" approach -- I prefer sending everything to one destination and then filtering/viewing using a good tool like Chainsaw or emacs ;)