You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Tomas Kloucek (JIRA)" <ji...@apache.org> on 2015/07/31 15:19:04 UTC
[jira] [Updated] (WICKET-5958) PageNumberEvictionStrategy(1)
crashes application if using ajax callback behaviours in Pages....
[ https://issues.apache.org/jira/browse/WICKET-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomas Kloucek updated WICKET-5958:
----------------------------------
Description:
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...
was:
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!
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...
> 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
> Priority: Critical
>
> 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)