cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <>
Subject RE: More problems with handle-errors
Date Tue, 19 Mar 2002 18:38:40 GMT
> From: Peter Robins []
> Say I want to catch 404 errors with something like this:
>    <map:handle-errors type="404">
>     <map:transform src="xslt/error2html.xsl"/>
>     <map:serialize/>
>    </map:handle-errors>
> If I only have 1 map:pipeline, this works fine: catches the error and
> executes the xsl.
> However, if I have >1 map:pipeline, it doesn't execute - I just get
> standard miaow from Tomcat. I tried putting it in all map:pipelines,
at the
> end of the last one, having it in its own map:pipeline (didn't like
> and nesting it in its own parent map:pipeline (didn't like that
> In the sample webapp supplied with cocoon, the handle-errors routine
> catch 404 errors either, but I see the syntax is different: instead of
> map:handle-errors having a type attribute, map:serialize has a
> attribute - presumably this just effects the output stream, and has no
> effect on the actual error-handling? If no type attribute is
> shouldn't it catch all errors?


Type attribute have the default of 500 (for backward compatibility), and
handler of type 500 does not processes 404 errors (for backward


Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message