cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: Logkit (I know, again) was [RT] Using Spring instead of ECM++
Date Mon, 13 Feb 2006 15:12:01 GMT
Hash: SHA1

On Mon, 13 Feb 2006, Berin Loritsch wrote:

> Date: Mon, 13 Feb 2006 09:58:06 -0500
> From: Berin Loritsch <>
> Reply-To:
> To:
> Subject: Re: Logkit (I know, again) was [RT] Using Spring instead of ECM++
> Niklas Therning wrote:
>>  Carsten Ziegeler wrote:
>> > 
>> >  Yes, please :) I would suggest log4j as commons-logging has problems
>> >  with classloading (afair) and noone is using jdk14 logging.
>>  Nowadays there's also slf4j ( Like commons-logging it's a
>>  facade for other logging frameworks but it doesn't suffer from the
>>  classloading problems of commons-logging. It's used by the Apache
>>  directory project. I think it's being developed by the guy behind log4j.
> Given the Avalon framework interfaces, we already have a log abstraction 
> using the LogEnabled and Logger interfaces.  Proper wrappers are also 
> provided for Log4J and have been for years.  There's no value add in 
> introducing YALF (Yet Another Logging Facade).

And we do have to maintain the contract mentioned interface requires for 
backward compatability to the dozends of component we already have.

- -- 
Giacomo Pati
Otego AG, Switzerland -
Orixo, the XML business alliance -
Version: GnuPG v1.4.2 (GNU/Linux)


View raw message