Return-Path: 
 <cocoon-dev-return-29288-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 29086 invoked by uid 500); 10 Jul 2002 11:50:59 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 29072 invoked from network); 10 Jul 2002 11:50:58 -0000
Message-ID: <3D2C1F85.1080608@apache.org>
Date: Wed, 10 Jul 2002 13:50:29 +0200
From: Nicola Ken Barozzi <nicolaken@apache.org>
Reply-To: nicolaken@apache.org
Organization: Apache Software Foundation
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.0) Gecko/20020530
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [PROPOSAL] Extending Sitemap Error Handling
References: 
 <Pine.LNX.4.43.0207101244150.5098-100000@fztig938.bank.dresdner.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


Michael Melhem wrote:
> Dear Cocoon community,
> 
> It seems to me that pipelines can only handle two error cases: 
 > Namely error 500 (General Exception) and error
 > 404 (ResourceNotFoundException).

Wrong.

> There appears to be no way currently to handle specific errors
 > that might be thrown by pipeline components other than to
 > render a general Error 500 page. Am I mistaken?

Yes.

> For example, it may be the case that a custom built generator could
 > throw custom Exceptions that a developer would like to
 > handle in a specific fashion.

Sure.
Make your Exception implement Notifying, and all the information you may 
need is in the generated xml and cen be taken from the environment.

> 
> To that end, I propose that pipeline be extendend so that it they can handle X number of errors depending on the amount of <map:handle-errors> defined in the sitemap for that pipeline.
> 
> <sitemap>
>   ...
> 
>   <map:handle-errors type="500">
>     <map:transform src="stylesheets/error2html.xsl"/>
>     <map:serialize/>
>    </map:handle-errors>
> 
>    <map:handle-errors type="404">
>     <map:transform src="stylesheets/error2html.xsl"/>
>     <map:serialize />
>    </map:handle-errors>
> 
>    <!-- one more or extra error-handles -->
>    <map:handle-errors type="someSpecificException">
>     <-- "type" here could me some sort of short code or the actual
>         full name of the Exception class? -->
>     <map:transform src="stylesheets/SpecificError2html.xsl"/>
>     <map:serialize status-code="500"/>
>    </map:handle-errors>
> 
>    etc..
> </sitemap>
> 
> Does anyone see any problems with this approach? Comments?

There is no need for this.
We just need a selector to select between errors inside handle-errors.

Why didn't you know this?
Because it's poorly documented.
Who is the sucker?
<ducking>  ;-P

Diana, there is a need for docs on error generation.
Where do I start?
(me lazy on docs and Andy Oliver kicks my butt for this ;-)

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org