On Wed, 29 Jun 2005, Bender Heri wrote:
> If you dont you pay special attention (i.e. using own
> RepositorySelector, using MDC, etc.), then all the log4j stuff is really
> global in one and them same JVM.
I think that would probably be okay. No?
> You need a way how you can distinguish your di
nesday, June 29, 2005 4:22 PM
> To: 'Log4J Users List'
> Cc: Bender Heri
> Subject: RE: new user question re: configuring log4j via code
>
>
> I call the LoggingConfiguration "class"/glorified-global near the
> start of the main() routine.
>
>
4J Users List
> Subject: RE: new user question re: configuring log4j via code
>
> Where and how do you call your LoggingConfiguration class exactly?
>
> The code "private static Logger log =
> Logger.getLogger(Foo.Bar.class);" is called at class loading,
> before any &q
Where and how do you call your LoggingConfiguration class exactly?
The code "private static Logger log = Logger.getLogger(Foo.Bar.class);" is
called at class loading, before any "real" code is executed.
In one JVM there is only one LogManager which has per default only one logger
repository. S
On Tue, 28 Jun 2005, Dave Gomboc wrote:
[small correction]
> public boolean someRoutine() {
>
> log.trace("Entered.");
>
> [boolean result = ;]
>
log.trace("Exiting: result = |{}|.", result);
return result;
> };
>
> };
