tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sofoklis Papasofokli (JIRA)" <...@tapestry.apache.org>
Subject [jira] Created: (TAPESTRY-2529) Handling Exceptions in Components by replacing/returning another component
Date Mon, 21 Jul 2008 11:19:31 GMT
Handling Exceptions in Components by replacing/returning another component
--------------------------------------------------------------------------

                 Key: TAPESTRY-2529
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2529
             Project: Tapestry
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.0.13
            Reporter: Sofoklis Papasofokli
            Priority: Minor


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.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message