You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "bernard (JIRA)" <ji...@apache.org> on 2013/01/24 21:25:14 UTC
[jira] [Comment Edited] (WICKET-5001) Recovery of bookmarkable Page
after Session Expiry
[ https://issues.apache.org/jira/browse/WICKET-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561945#comment-13561945 ]
bernard edited comment on WICKET-5001 at 1/24/13 8:24 PM:
----------------------------------------------------------
We have IPageSettings#getRecreateMountedPagesAfterExpiry(). This setting should work. If a page is mounted then Wicket must re-create it on expiry. The application can control behavior further by managing fallback in the default page constructor. So no need for Wicket to make any assumptions. It already works in some cases but not in others e.g. because of a bug (see WICKET-4997).
I am frustrated because we don't have a workaround method in Wicket 6.5 as in 1.4 (please refer to the 1.4 test case in WICKET-4014).
was (Author: bht@actrix.gen.nz):
We have IPageSettings#getRecreateMountedPagesAfterExpiry(). This setting should work. If a page is mounted then Wicket must re-create it on expiry. The application can control behavior further by managing fallback in the default page constructor. So no nneed for Wicket to make any assumptions. It already works in some cases but not in others e.g. because of a bug (see WICKET-4997).
I am frustrated because we don't have a workaround method in Wicket 6.5 as in 1.4 (please refer to the 1.4 test case in WICKET-4014).
> Recovery of bookmarkable Page after Session Expiry
> --------------------------------------------------
>
> Key: WICKET-5001
> URL: https://issues.apache.org/jira/browse/WICKET-5001
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.4.0
> Environment: Java 7, GlassFish 3.1.2.2
> Reporter: bernard
> Attachments: Testcase.zip
>
>
> Some efforts were made since 1.5 to reduce occurrences of PageExpiredException or at least the impact of it.
> Please see WICKET-4014
> With Wicket 6.4.0 it appears that a simple test case does not produce the expected results.
> The attached quickstart tests a page containing a form. The page does not have any meaningful state.
> Therefore, after session expiry Wicket should call the default constructor and execute form submit or link onclick without any problems.
> There is no difference in outcome that could be expected before and after expiry.
> In real life, if the page was constructed with an IModel constructor, of course the model would not exist after expiry but that could be handled in the default constructor that is called after expiry.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira