Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 45718 invoked from network); 6 Apr 2004 14:13:55 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Apr 2004 14:13:55 -0000 Received: (qmail 81427 invoked by uid 500); 6 Apr 2004 14:13:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 81322 invoked by uid 500); 6 Apr 2004 14:13:40 -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 81204 invoked from network); 6 Apr 2004 14:13:38 -0000 Received: from unknown (HELO warden.diginsite.com) (208.29.163.248) by daedalus.apache.org with SMTP; 6 Apr 2004 14:13:38 -0000 Received: from wlvims01.diginsite.com by warden.diginsite.com via smtpd (for daedalus.apache.org [208.185.179.12]) with SMTP; Tue, 6 Apr 2004 07:13:40 -0700 Received: from WLVIMS01 ([127.0.0.1]) by WLVIMS01.digitalinsight.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with SMTP id com for ; Tue, 6 Apr 2004 07:13:39 -0700 Received: by calexc01.diginsite.com with Internet Mail Service (5.5.2657.72) id <22RFF2KP>; Tue, 6 Apr 2004 07:12:40 -0700 Message-ID: <31DF72A980E5D511B48C000102BD8685061DB2FF@calexc01.diginsite.com> From: Ralph Goers To: "'dev@cocoon.apache.org'" Subject: RE: Logging all requests Date: Tue, 6 Apr 2004 07:12:33 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I was just looking into this over the last week. Unfortunately, neither the process method or anything in CocoonServlet provide a hook to log or capture the kind of statistics you want. In my case, I am adding some JMX statistics. The only way I see to do it, short of modifying one of the classes, is to use a servlet filter. That should also work for you. Ralph -----Original Message----- From: Surjan Singh [mailto:surjan.singh@misgl.com] Sent: Tuesday, April 06, 2004 4:08 AM To: dev@cocoon.apache.org Subject: Logging all requests Hello, I'd like to log all Requests so that we can record them for analysis. So, far the only way I think I can do this is to modify the method process(..) in org.apache.cocoon. In this method, I thought I could use a logging component (which has yet to be created) from the component manager and (if it exists) to invoke a log method on it. What do you think? Is this the right way to go about this? Surj