James Taylor wrote:
On Sun, 2002-12-08 at 18:15, Jon Scott Stevens wrote:

on 2002/12/8 2:37 PM, "Nicola Ken Barozzi" <[EMAIL PROTECTED]> wrote:


What about Avalon logging? It's better suited for server-side logging,
and has its own abstractions that make it possible to use as
implementations log4j, logkit or whatever.
I prefer that we use commons-logging.

I'm -1 on Avalon logging as the dependency simply because I like to have the
choice as to which logging package I want to use.

One thing we might consider is not requiring LogKit as the logger, but
still use an IOC style of log configuration like in Avalon. In fact, we
could still use the LogEnabled / Logger facade without restricting log
configuration options.
Exactly.

Avalon Logging != Logkit

I'm not suggesting that you use Logkit, but the Avalon logging interface and facades. the Logger is part of the Avalon lifecycle, and it's very important, also from a security perspective, that it's given by the container, not gotten by the Component, and makes management of it easier.

This may not be appropriate for t2 but I think it will make sense for
t3. One of the nice things about IOC in this case is that the container
can build / obtain the logger it provides in any way. Thus, for example,
if you have a scenario where class loading discovery is not workable,
you can eliminate it without having to touch the components, just the
managers.
Exactly.

The simply -1 doesn't stand because using Avalon logging it's possible to use any logging implementation you wish.

Look in the framework:
http://cvs.apache.org/viewcvs/jakarta-avalon/src/java/org/apache/avalon/framework/logger/

AbstractLogEnabled.java
AvalonFormatter.java
ConsoleLogger.java
Jdk14Logger.java
Log4JLogger.java
LogEnabled.java
LogKit2AvalonLoggerAdapter.java
LogKitLogger.java
Logger.java
NullLogger.java


-- jt, who is almost completely converted to avalon now.
:-)

--
Nicola Ken Barozzi                   [EMAIL PROTECTED]
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to