Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 73307 invoked from network); 21 Feb 2008 15:19:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Feb 2008 15:19:27 -0000 Received: (qmail 32821 invoked by uid 500); 21 Feb 2008 15:19:19 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 32764 invoked by uid 500); 21 Feb 2008 15:19:19 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 32753 invoked by uid 99); 21 Feb 2008 15:19:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2008 07:19:19 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of insomniacpenguin@googlemail.com designates 64.233.182.190 as permitted sender) Received: from [64.233.182.190] (HELO nf-out-0910.google.com) (64.233.182.190) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2008 15:18:45 +0000 Received: by nf-out-0910.google.com with SMTP id f5so32700nfh.8 for ; Thu, 21 Feb 2008 07:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=gMFgfARferVNFvY+SfnNLsqGW2OVzEp/lo20xGtOixI=; b=JPZ6sYwpdukwN46RSJ0/yn+gb922zd76EU7PLM3wZyxLM991pk4PmKzLgipYjnx5tEFw8q8m+LGEoBNctHb5aezFVut69Hbt4rEY7+DoJv11bO4Dsi5XqbH924VtuJ8PfduByniv/anXVLslDSeDXfsN/108xfDo16IWbgmRZb8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JqLvP02n3MnI7SoSel743k9XaVB9Tlntc2Y6thIZ1E3NuiA+4AnogKC6eiicSveL8tr7LF05bbh/UOhBcoNFpBbJ/7uq2J3XAwse8l4SLoqWxnOJJHv2qYjZi/zr8Mu2Tr30faZ2/mjaydlFzUAuEHRikoP7jQ7VIW9aTkCNmg8= Received: by 10.78.171.20 with SMTP id t20mr15883351hue.20.1203607130451; Thu, 21 Feb 2008 07:18:50 -0800 (PST) Received: by 10.78.187.12 with HTTP; Thu, 21 Feb 2008 07:18:50 -0800 (PST) Message-ID: Date: Thu, 21 Feb 2008 15:18:50 +0000 From: "Andy Stevens" To: users@cocoon.apache.org Subject: Re: How to log/trace functional information ?? In-Reply-To: <47B479F0.6050204@meteo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <47B479F0.6050204@meteo.fr> X-Virus-Checked: Checked by ClamAV on apache.org On 14/02/2008, S=E9bastien Geindre wrote: > A client send xml data. > I need to put it in kind of database. > This is ok. > > But i would like to write in a file (for example) that client A send > this datas, this day,... > All information i need to trace are in the xml data sent. > > A kind of monitoring, or functional trace. > > How can i do that with C2.2 ? Are you passing the user's document through a sitemap pipeline? If so, you could include a custom transformer that passes everything through unchanged, but watches for the values you're interested in and records them. Then in the endDocument callback, write them to the log file. Don't see any reason why 2.2 would be any different from 2.1 with this approach, asides from component lifecycle code. Andrew. --=20 http://pseudoq.sourceforge.net/ Open source java Sudoku application --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org