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 98861 invoked from network); 21 Mar 2000 17:17:08 -0000 Received: from lotus2.lotus.com (192.233.136.8) by locus.apache.org with SMTP; 21 Mar 2000 17:17:08 -0000 Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id MAA10043 for ; Tue, 21 Mar 2000 12:32:56 -0500 (EST) From: Scott_Boag@lotus.com Received: from cammail04.lotus.com (CAMMAIL04.lotus.com [9.95.4.116]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id MAA03567 for ; Tue, 21 Mar 2000 12:16:19 -0500 (EST) Subject: Re: Plan for Pipeline Logging To: cocoon-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0 March 30, 1999 Message-ID: Date: Tue, 21 Mar 2000 12:13:55 -0500 X-MIMETrack: Serialize by Router on CAMMAIL04/CAM/M/Lotus(Release 5.0.2c |February 2, 2000) at 03/21/2000 12:13:27 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi Robin. Depending on how closely coupled with Xalan you want to be, you might take a look at the Xalan "listener" interfaces, which are there for the purposes of debugging. -scott "Robin Green" cc: (bcc: Scott Boag/CAM/Lotus) Subject: Plan for Pipeline Logging 03/21/00 09:17 AM Please respond to cocoon-dev I would like to have a look at the intermediate result trees generated during the Cocoon processing pipeline (and even just the output tree, since my pages are generating a malformed meta refresh tag, so I can't even see the result page in IE!) for debugging purposes, so I am working on a new logger level, "pipeline", which will log each intermediate result tree to a separate file in the repository (probably calling them foo$1.xml, foo$2.xml etc). Of course the Xalan command-line executor can be used for simple debugging, but if XSP or request parameters are involved, it's best to debug in Cocoon directly. I plan to encapsulate the Repository code in a very small class org.apache.cocoon.store.repository.Repository since it will be used by both XSP and the pipeline logger, and to change the property name from "processor.xsp.repository" to "repository.dir" (keeping the comments attached) since it will no longer be just about XSP necessarily. Also moving some of the IO util methods to org.apache.cocoon.IOUtils, just for tidyness. Does this sound okay or am I stepping on any toes? P.S. This is Cocoon-1.7.1dev I am talking about here. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com