[
https://issues.apache.org/jira/browse/WICKET-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ertl resolved WICKET-4355.
--------------------------------
Resolution: Fixed
fixed in trunk for 1.4
> make client-side redirects easier by introducing RedirectException
> ------------------------------------------------------------------
>
> Key: WICKET-4355
> URL: https://issues.apache.org/jira/browse/WICKET-4355
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.19
> Reporter: Peter Ertl
> Assignee: Peter Ertl
> Priority: Minor
> Fix For: 1.4.20
>
>
> In wicket 1.5 and 6.0 we have RestartResponseException with a redirect policy
> to enforce a client side redirect. In 1.4 we need the following code fragment:
> getRequestCycle().setRedirect(true)
> throw new RestartResponseException(page)
> Since client-side redirects to pages are very common I find it discouraging
> that wicket users have to get into some of the guts of request cycle just to
> understand the above fragment. Also client-side redirects will not work with
> page instances like here
> getRequestCycle().setRedirect(true)
> throw new RestartResponseException(new MyPage())
> By introducing RedirectException this very(!) common use case will be a lot
> easier and more terse and though we want people to migrate to 1.5 or, even
> better, 6.0 it will not hurt to give some love to 1.4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
