[
https://issues.apache.org/jira/browse/WICKET-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Maes updated WICKET-313:
--------------------------------
Attachment: wicket-313.patch
This is a patch to get an uniform behavior with the RuntimeException in the
RequestCycle steps.
The RuntimeException during respond is no more catched in the AjaxRequestTarget
but is recovered in the RequestCycle to be processed like other exceptions.
Moreover, it was necessary to make EncodingResponse extend WebResponse in order
to get the redirect(String url) method in case an ajax response failed in the
respond step. In that way, when an error occurs in the respond step of an ajax
request, the client is redirected to the error page.
> 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
>
> Attachments: wicket-313.patch
>
>
> 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.
