You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2011/08/12 00:20:27 UTC

[jira] [Closed] (TAP5-198) Handling Exceptions in Components by replacing/returning another component

     [ https://issues.apache.org/jira/browse/TAP5-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Massimo Lusetti closed TAP5-198.
--------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.3

Please open a new one for 5.3 if this still applicable

> Handling Exceptions in Components by replacing/returning another component
> --------------------------------------------------------------------------
>
>                 Key: TAP5-198
>                 URL: https://issues.apache.org/jira/browse/TAP5-198
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Sofoklis Papasofokli
>            Priority: Minor
>             Fix For: 5.3
>
>
> When an exception occurs in a component, database/null pointer etc something that breaks the component, the exception propagates to the page and currently we show some error page.
> Unfortunately this breaks the whole page. I think it would be nice to have a way to define an error component to replace the one that brakes, so we lose only the component and not the whole page, something similar with have onException() and returning the error page. 
> Currently we cant find a way to do that.
> Thanks,
> Sofoklis

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira