logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: multiple components using log4j causes problems
Date Fri, 11 Jan 2002 14:25:28 GMT

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:
>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 problem 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 this?
>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