[
https://issues.apache.org/jira/browse/WICKET-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477029
]
Jean-Baptiste Quenot commented on WICKET-313:
---------------------------------------------
I have the same problem here, but not the same usecase. When the client issues
an Ajax request, my application sometimes throws an exception in
WebRequestCycle.processEventsAndRespond(), and sometimes it is thrown in
WebRequestCycle.respond(). And each case does not exhibit the same behavior:
an error in processEventsAndRespond() generates a window.location=<error page>
response, whereas an error in respond() in caught and muted by
AjaxRequestTarget (only logged at error level). IMO we need an uniform
behavior, so AjaxRequestTarget should not catch any exception, and let it
propagate. So I'm +1 on your proposal.
> AjaxRequestTarget error handling
> --------------------------------
>
> Key: WICKET-313
> URL: https://issues.apache.org/jira/browse/WICKET-313
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Oscar Bueno
> Assigned To: Jean-Baptiste Quenot
> Fix For: 2.0
>
>
> Now the respond method of the AjaxRequestTarget is catching all the
> RuntimeExceptions that are throwed. I would prefer to handle this exceptions
> by myself. I have a requestTarget that is a wrapper of the wicket
> AjaxRequestTarget where we could made something in case of errors in the
> respond method of the AjaxRequestTarget.
> I'm using the AjaxRequestTarget to replace a wizard panel, in case of error,
> I would display an errors panel instance of the original panel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
