[jira] Commented: (WICKET-908) There is no way to specify what exceptions to log in RequestCycle

["Juergen Donnerstag (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524260 ] 

Juergen Donnerstag commented on WICKET-908:
-------------------------------------------

sorry, I reverted that change. logRuntimeExcpeiton can be replace easily already.

> There is no way to specify what exceptions to log in RequestCycle
> -----------------------------------------------------------------
>
>                 Key: WICKET-908
>                 URL: https://issues.apache.org/jira/browse/WICKET-908
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>            Reporter: Marat Radchenko
>            Assignee: Juergen Donnerstag
>            Priority: Critical
>             Fix For: 1.3.0-beta4
>
>
> RequestCycle, line 1135 logs all exceptions except for PageExpiredException. This is not a wanted behavior for us (for example, it also logs AuthorizationException which is not a error).
> So we need some way to specify which exceptions should be treated as errors and which ones are just need to be handled by RequestCycleProcessor#respond(RuntimeException, RequestCycle).
> Maybe there is some way to globally catch application exceptions other than writing a custom RequestCycleProcessor. If so then tell me please.
> The possible solution is to move exception logging to RequestCycleProcessor#respond(RuntimeException, RequestCycle) because it can be overriden.

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