[
https://issues.apache.org/jira/browse/WICKET-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680080#comment-14680080
]
Martin Grigorov commented on WICKET-5958:
-----------------------------------------
About the backporting: we may decide to do that later but first we want to see
that it doesn't break 7.x somehow. 6.x is used by many apps already in
production and it is not that easy decision to change some behavior.
About "Wicket 7 requires JDK 7": JDK 7 has been EOL-ed this year. JDK 6.x has
been EOL-ed few years ago... It is hard to convince someone who spends his/her
spare time on open source projects with such reasons! You can seek for paid
help though!
About new/old page: the page number is per http session, not per browser tab.
If you have N tabs with ajax timers in their pages then you have N live pages.
Since you use page store with size 1 page then you will hit
PageExpiredException for then N+1 page.
> 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)
