Log wars #23 [ was [VOTE] CommonsLogger.java]

[Paul Hammant]

Nicola,

I understand what you mean. We already have facades, why put in a facade to a facade that does the same thing our facades do?
In fact, why not deprecate our facades and use the commons logging ones?

Talking about the "real" solution, it would seem that it would involve these steps:

1) Utility packages like jakarta commons ones use commons-logging.
It's the easiest and most sensible solution for fine grained stuff.

I'd disagree. I am fond of the no-logging design for reusable beans (use a monitor concept instead).

2) Avalon Framework uses commons-logging as the facade for logging to
different implementations. This means that coarse-grained components
keep using AF4-compatible IOC.

Correction:- "Avalon Framework facilitates CommonsLogging at instance level" (CommonsLogEnabled, AbstractCommonsLogEnabled).

 3) Every Avalon container registers it's own LogFactory as a top-level
    LogFactory, so that it intercepts *all* logging calls and can deal
    with them in a centralized way, somewhat inverting the control.

I did much experimentation some months ago. It is not so easy. If we can eradicate the static nature to Commons-Logging (and most importantly its usages in Commons) we have a chance of making it work. C-L was not designed at all with IoC in mind...

- Paul


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