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 2014/01/15 15:29:20 UTC
[jira] [Commented] (WICKET-5471) Store the page if it is known that
it will be used in a following request
[ https://issues.apache.org/jira/browse/WICKET-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872119#comment-13872119 ]
Martin Grigorov commented on WICKET-5471:
-----------------------------------------
Workaround until Wicket 6.14.0 is released:
call Session.get().getPageManager().touch(page) before page.getPageReference()/setResponsePage(page).
> Store the page if it is known that it will be used in a following request
> -------------------------------------------------------------------------
>
> Key: WICKET-5471
> URL: https://issues.apache.org/jira/browse/WICKET-5471
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.13.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Fix For: 6.14.0, 7.0.0
>
>
> WICKET-5415 added optimization that a page that is not touched (respectively initialized/rendered) won't be stored in the IPageStore/IDataStore.
> This led to a problem like the one described at https://issues.apache.org/jira/browse/SYNCOPE-476 - a PageReference returns null.
> Wicket can make this better by initializing a page which #getPageReference() is used or when RequestCycle#setResponsePage(Page) is used.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)