You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2012/07/23 11:44:36 UTC

[jira] [Resolved] (WICKET-4647) Use NonResettingRestartResponseException for setResponsePage

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

Martin Grigorov resolved WICKET-4647.
-------------------------------------

    Resolution: Won't Fix

This improvement wont be applied for now because of the reasons pointed by Bertrand.
If someone needs such optimization then (s)he can throw one of the replacement exceptions instead of using setResponsePage()
                
> Use NonResettingRestartResponseException for setResponsePage
> ------------------------------------------------------------
>
>                 Key: WICKET-4647
>                 URL: https://issues.apache.org/jira/browse/WICKET-4647
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.5.7
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>            Priority: Minor
>
> WICKET-4636 made an improvement in Wicket rendering process by skipping the rendering of a page if there is a scheduled request handler after the current one.
> A further optimization may be made by throwing NonResettingRestartResponseException from WICKET-4637 when setResponsePage() is used. This way even when setResponsePage() is during the rendering (e.g. in onBeforeRender()) Wicket will be able to stop the rendering and thus save some CPU cycles.

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