logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Master" <tmas...@iknowledgeinc.com>
Subject Re: multiple components using log4j causes problems
Date Fri, 11 Jan 2002 17:08:07 GMT
I stopped using a (properties) config file to initialise log4j.
Instead i parse it and create instances myself of the objects i need.  I
don't have a large number of objects to create so this is trivial for me.
I also give my own categories and appenders their own naming prefix,  just
incase the appserver I use uses log4j too.  Safer and prevents conflicts.

T Master

----- Original Message -----
From: "Aron Kramlik" <aron.kramlik@itouch.com.au>
To: "Log4J Users List" <log4j-user@jakarta.apache.org>
Sent: Saturday, January 12, 2002 2:34 AM
Subject: Re: multiple components using log4j causes problems

> Ceki,
> Thanks for the response, I will mention this to them and wait for a
> response.
> What strategies would you recommend for internal development of libraries
> and components that we could use to ease the pain associated with this?
> Aron.
> aron.kramlik@itouch.com.au
> iTouch Australia
> ----- Original Message -----
> From: "Ceki Gülcü" <ceki@qos.ch>
> To: "Log4J Users List" <log4j-user@jakarta.apache.org>
> Sent: Friday, January 11, 2002 6:25 AM
> Subject: Re: multiple components using log4j causes problems
> This is a very serious problem. The new log4j API allows the main
> program to install a RepositorySelector which can control the
> hierarchy to be used depending on the context, for example depending
> on the enterprise application. However, this requires support from the
> application server because only the application server (e.g. JBoss)
> controls the context.
> In short log4j has the required pluggable interface, the application
> server writers need to jump on the wagon. I suggest that you mention
> the problem to the JBoss people also mentioning the new RepositorySelector
> API in log4j.
> At 00:15 12.01.2002 -0800, Aron Kramlik wrote:
> >Hi!
> >
> >We are coming across a bit of a problem where more and more third party
> >libraries and applications are using log4j for their logging.  The
> comes
> >when JBoss or OpenJMS and third party libraries are all doing their
> initialisation
> >of log4j and we need to as well when we deploy our components.
> >
> >Have other faced this problem?  What are the suggested practices for
> >
> >Thanks.
> >
> >Aron.
> >
> >aron.kramlik@itouch.com.au
> >iTouch Australia
> --
> Ceki Gülcü - http://qos.ch

To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

View raw message