From dev-return-84615-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Mon Feb 13 14:58:35 2006 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 21930 invoked from network); 13 Feb 2006 14:58:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Feb 2006 14:58:33 -0000 Received: (qmail 75374 invoked by uid 500); 13 Feb 2006 14:58:25 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 75281 invoked by uid 500); 13 Feb 2006 14:58:25 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 75270 invoked by uid 99); 13 Feb 2006 14:58:25 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2006 06:58:25 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of bloritsch@d-haven.org designates 65.212.180.79 as permitted sender) Received: from [65.212.180.79] (HELO pyramid-04.kattare.com) (65.212.180.79) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2006 06:58:23 -0800 Received: from [127.0.0.1] ([66.208.12.142]) (authenticated bits=0) by pyramid-04.kattare.com (8.12.11/8.12.11) with ESMTP id k1DEvxs5020745 for ; Mon, 13 Feb 2006 06:58:02 -0800 Message-ID: <43F09E7E.4010103@d-haven.org> Date: Mon, 13 Feb 2006 09:58:06 -0500 From: Berin Loritsch User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Logkit (I know, again) was [RT] Using Spring instead of ECM++ References: <43E8F7FF.4070304@apache.org> <43E9CB85.9020605@mobilebox.pl> <43ECB985.7060500@reverycodes.com> <43ECDDC9.8070909@apache.org> <43ECE244.2040109@apache.org> <43F083FD.3040908@apache.org> <43F08EC1.6040902@apache.org> <43F09B0A.5030804@trillian.se> In-Reply-To: <43F09B0A.5030804@trillian.se> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 (www.slf4j.org). 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). In the future when your components have no ties to Avalon, just use Log4J directly.