From bloritsch@infoplanning.com Wed Nov 1 15:58:39 2000 Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 29971 invoked from network); 1 Nov 2000 15:58:39 -0000 Received: from www.saic.com (HELO cp-its-www) (198.151.15.15) by locus.apache.org with SMTP; 1 Nov 2000 15:58:39 -0000 Received: from johnnybravo (fw.infoplanning.net [209.8.58.131]) by cp-its-www (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with SMTP id HAA00120 for ; Wed, 01 Nov 2000 07:57:36 -0800 Message-ID: <00b501c0441c$5c3823d0$bd00a8c0@infoplanning.com> From: "Berin Loritsch" To: Subject: Cocoon Logging Date: Wed, 1 Nov 2000 10:56:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Avalon has a pretty decent and flexible logging mechanism that we could use in Cocoon. Is this something that we want to apply to Cocoon? It would allow us to have one logging mechanism regardless of Cocoon invocation method. The log mechanism would be one more jar, "log.jar". It would give us the flexibility of log channels and levels. That way we can pepper the code with plenty of INFO or DEBUG logging commands that would really help in locating errors--and the ability to ignore those in production. --------------------------------------- If you lust for Ham and Eggs, you have committed breakfast in your heart already. -- C. S. Lewis