Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <424D85D8.5020208@reverycodes.com>
Date: Fri, 01 Apr 2005 12:33:12 -0500
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: core logging
References: <d2cmkm$rl$1@sea.gmane.org> <424AFC97.8080409@reverycodes.com>
 <d2f2ih$pgs$1@sea.gmane.org>
In-Reply-To: <d2f2ih$pgs$1@sea.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jorg Heymans wrote:
> 
> It would be nice to have an easy to trace logfile where one can
> follow sequentially how a request is processed, what main components are 
> involved, when they are called, how they affect the response etc 
> (basically the things you can find out with a debugger).

There is SimpleSitemapExecutor in 2.2 - probably that's what you want.


> This would also make it easier for beginning cocooners to learn the core 
> cocoon concepts (sitemap,matchers,gen|tran|ser|act,flow,forms) and how 
> they play together.
> 
> Can something like this be implemented with clever logging targets only?

As far as I see in 2.1 messages such as:

DEBUG (2005-04-01) 12:29.15:698 [sitemap] (/) PoolThread-4/PreparableMatchNode: 
Matcher 'wildcard' matched prepared pattern '' at 
file:/C:/Work/Apache/cocoon-2.1.X/build/webapp/sitemap.xmap:525:27

all go to [sitemap] target at DEBUG level - which makes filtering hard :-)


Vadim