commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: Resisting the temptation
Date Fri, 10 May 2002 22:06:40 GMT
At 14:47 10.05.2002 -0500, Richard Sitze wrote:
>If the interface is based on the commons logging factory then the logger
>(Log4J presumably) is already set by the time Log4J is encountered (else it
>would go elsewhere).
>
>If not, the current default is going to go to Log4J anyway...  How SHOULD a
>logger implementation bootstrap itself into commons logging, assuming it
>wants to use a logger internally?
>
>If these things are set in a manifest, what will happen if Log4J is in the
>path AND we aren't using it,or worse we ARE using it in another component
>of the system.  Will it force everything to the one logger?

Good question.


--
Ceki


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


Mime
View raw message