Return-Path: 
 <dev-return-61850-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 57080 invoked from network); 4 Jun 2004 02:04:47 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 4 Jun 2004 02:04:47 -0000
Received: (qmail 82741 invoked by uid 500); 4 Jun 2004 02:05:02 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 82715 invoked by uid 500); 4 Jun 2004 02:05:01 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 82700 invoked by uid 99); 4 Jun 2004 02:05:01 -0000
Received: from [217.160.230.41] (HELO mout.perfora.net) (217.160.230.41)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 03 Jun 2004 19:05:01 -0700
Received: from 209.237.227.194 (helo=[127.0.0.1])
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 1BW44M-0gPQ-0MKyxe-0005se; Thu, 03 Jun 2004 22:04:30 -0400
Message-ID: <40BFD8AD.3020405@reverycodes.com>
Date: Thu, 03 Jun 2004 22:04:29 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7) Gecko/20040514
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: error handling
References: <40BF27B5.6020906@vafer.org>
In-Reply-To: <40BF27B5.6020906@vafer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Torsten Curdt wrote:

> I have an interal pipeline which sometimes
> throws an exception due to broken links.
>
>   <map:pipeline>
>     <map:generate type="html" src="get/{1}"/>
>     <map:serialize type="xml"/>
>     <map:handle-errors>
>       <map:generate src="default.xml"/>
>       <map:serialize type="xml"/>
>     </map:handle-errors>
>   </map:pipeline>
>
> And another one using it
>
>   <map:pipeline>
>     <map:generate src="whatever.xml"/>
>     <map:transform type="cinclude"/> --> calls the intenal pipeline
>     ...
>   </map:pipeline>
>
> Using the first pipeline works just
> fine. Exceptions are being caught and
> a default xml file is being presented
> instead.
>
> Unfortunately using it through the
> second pipeline (through the cinclude
> transformer) brings up the exception.
>
> Anyone a clue what's happing here?


IIRC, last first friday we had a chat with Carsten about adding an 
attribute to the <handle-errors/> or to the <pipeline/> which will 
indicate what behavior is needed in case of internal request: throw 
exception or process <handle-errors/>. Carsten?

Vadim