You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Peter Stavrinides (JIRA)" <ji...@apache.org> on 2009/02/11 11:37:00 UTC

[jira] Commented: (TAP5-44) enable creation of custom "onException" event handler

    [ https://issues.apache.org/jira/browse/TAP5-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672579#action_12672579 ] 

Peter Stavrinides commented on TAP5-44:
---------------------------------------

I think a couple of methods like that would really help to determine what to do with exceptions, for example:
- checked exceptions you may want to handle in the interface and recover from them gracefully
- unchecked exceptions could be reported to a ticketing system
- logging ?

I have this requirement so do this all manually, its quite difficult to maintain.  



> enable creation of custom "onException" event handler
> -----------------------------------------------------
>
>                 Key: TAP5-44
>                 URL: https://issues.apache.org/jira/browse/TAP5-44
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Kristian Marinkovic
>
> make it possible to create custom "onException" event handler that are fired when custom Exceptions are thrown.
> i have the use case saying, that when an optimistic lock exception is thrown the same page with the newly loaded entity and an error message has to be displayed. Although it is possible to use the "onException" event it would be much nicer to have a "onExceptionFromOptimisticLocking" exception where the developer can put the exception handling into this specific method. In the near future we will have multiple other exceptions that need to be handled in a similar way. 
> i prefer specific event handler to a bunch of instanceof  statements 

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