[jira] [Resolved] (WICKET-3347) Simplify somehow the code in org.apache.wicket.request.handler.render.WebPageRenderer.respond(RequestCycle)

["Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3347.
-------------------------------------

    Resolution: Won't Fix

No easy way to simplify this at the moment.
At least it has good coverage of unit tests.
                
> Simplify somehow the code in org.apache.wicket.request.handler.render.WebPageRenderer.respond(RequestCycle)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3347
>                 URL: https://issues.apache.org/jira/browse/WICKET-3347
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.5-M3
>            Reporter: Martin Grigorov
>
> The code in org.apache.wicket.request.handler.render.WebPageRenderer.respond(RequestCycle) decides whether to redirect or directly render the current page depending on several conditions:
>  - is Ajax request
>  - the redirect policy (org.apache.wicket.request.handler.RenderPageRequestHandler.RedirectPolicy)
>  - the render strategy (org.apache.wicket.settings.IRequestCycleSettings.RenderStrategy)
>  - whether the page is stateless
> All these conditions lead to complex and fragile code.
> We have to think how to improve this.

--
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