[
https://issues.apache.org/jira/browse/WICKET-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679988#comment-14679988
]
Martin Grigorov commented on WICKET-5958:
-----------------------------------------
With the same success you can set the max number of pages to 0 and expect that
it will work...
If you have 2 browser tabs with Ajax-ified pages in them then you have 2 alive
pages. Simple!
You can re-design this by using stateless Ajax behavior instead of Wicket's
stateful default ones. See
https://github.com/wicketstuff/core/tree/master/jdk-1.7-parent/stateless-parent
for more information. I'm not sure it provides a timer behavior implementation
yet. With a stateless Ajax behavior each request will create a fresh new page
instance.
About the preserving of the page parameters: I think this is improved in 7.0.0.
> PageNumberEvictionStrategy(1) crashes application if using ajax callback
> behaviours in Pages....
> ------------------------------------------------------------------------------------------------
>
> Key: WICKET-5958
> URL: https://issues.apache.org/jira/browse/WICKET-5958
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.20.0
> Environment: All operation systems.
> Reporter: Tomas Kloucek
> Attachments: myproject.zip
>
>
> As I promised in
> http://apache-wicket.1842946.n4.nabble.com/Howto-have-just-currently-viewed-page-in-session-td4671631.html
> , here is the promised demo.
> You've got there two pages, HomePage and RedirectPage, both with Ajax timer.
> First page is with redirect link. If you press that redirect link you're
> redirected to RedirectPage page, but that page is recreated without
> pageparameters eventually and application crashes with:
> Caused by: java.lang.IllegalArgumentException: Page parameters cannot be
> empty!
> at com.mycompany.myproject.RedirectedPage.<init>(RedirectedPage.java:26)
> If I look at PageProvider class and resolvedPageInstance method, it's clear
> why it crashes....
> But guys, as a page store developer, I want to have just currently viewed
> page in session, nothing more! When redirecting I don't care about previous
> page ajax callbacks...
> This bug is critical for us, so please do not lower the priority and please
> help us with it.
> Btw, yes, raising number of saved pages solves the problem, but this is not
> preferred solution for us, because we support multiple opened browser
> tabs.,,And it's causing me problems in page management...
> Looking forward for solution or at least tips...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
