cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Fagerstrom (JIRA)" <>
Subject [jira] Closed: (COCOON-1954) [Patch] RequestProcessor swallows exceptions in blocks case
Date Mon, 19 Feb 2007 08:13:06 GMT


Daniel Fagerstrom closed COCOON-1954.

    Resolution: Fixed

> [Patch] RequestProcessor swallows exceptions in blocks case
> -----------------------------------------------------------
>                 Key: COCOON-1954
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core, - Blocks Framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Alexander Klimetschek
>         Attachments: cocoon-request-processor-swallows-exceptions-for-blocks.patch
> While updating to the latest Cocoon I stepped into the problem that you cannot see the
exceptions thrown in a BlockServlet called by another one, since the new refactored RequestProcessor
swallows all exceptions. The generated error page is fed into the response output stream which
is eventually read by anything in the calling pipeline, which mostly cannot handle that html
error page (in my case it gets some xml) and will throw another exception like SAXParseException.
> This patch adds a boolean rethrowExceptions() method to the RequestProcessor that is
used inside service() to check whether a catched exception should be rethrown. The standard
return value is false, in the subclass o.a.c.sitemap.SitemapServlet$RequestProcessor it returns
true so that the exception is passed on to the "root" sitemap (handling the servletrequest
that actually comes from a browser or so) which will eventually create the error page.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message