Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 83274 invoked from network); 27 May 2004 13:07:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 27 May 2004 13:07:26 -0000 Received: (qmail 58107 invoked by uid 500); 27 May 2004 13:06:22 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 57752 invoked by uid 500); 27 May 2004 13:06:17 -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 Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 57519 invoked by uid 98); 27 May 2004 13:06:15 -0000 Received: from cziegeler@s-und-n.de by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(212.8.217.2):. Processed in 0.09417 secs); 27 May 2004 13:06:15 -0000 X-Qmail-Scanner-Mail-From: cziegeler@s-und-n.de via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(212.8.217.2):. Processed in 0.09417 secs) Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by hermes.apache.org with SMTP; 27 May 2004 13:06:14 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 7E59819F6B2 for ; Thu, 27 May 2004 15:06:07 +0200 (CEST) Received: from hw0386 ([10.10.2.43]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004052714573789-6435 ; Thu, 27 May 2004 14:57:37 +0200 From: "Carsten Ziegeler" To: "Cocoon-Dev" Subject: [RT] Logging in Cocoon Date: Thu, 27 May 2004 15:05:56 +0200 Organization: S&N AG MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-Index: AcRD61kJK8ZJIXOhSqKvCLb1650mLg== X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 27.05.2004 14:57:38, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 27.05.2004 14:57:38, Serialize complete at 27.05.2004 14:57:38 Message-ID: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Many have suggested this in the past and as Ugo mentioned it yesterday, I think it's time to check our logging strategy. Currently we use LogKit as our base logging system. Unfortunately we are using third party components that either use Log4J or commons-logging. So in the end you have to configure more than one logging system. Log4j is the standard for logging - I think this is obvious. So, the easiest and most obvious solution is to use Log4J in Cocoon as well. Since 2.1.5 you can simply switch to Log4J if you configure the logger-class parameter in web.xml. There is only one drawback: log4j has to be configured "elsewhere"; this is not done by Cocoon. So, my suggestion is to: - deprecate the use of LogKit - switch to log4j as default - make it possible to configure log4j from within Cocoon (like the current logkit.xml for LogKit). WDYT? Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.osoco.net/weblogs/rael/