[
https://issues.apache.org/jira/browse/WICKET-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680056#comment-14680056
]
Tomas Kloucek commented on WICKET-5958:
---------------------------------------
"About the preserving of the page parameters: I think this is improved in
7.0.0."
This isn't good news..:-( Martin, nobody will give me time to upgrade or
redesign our FE layer to Wicket 7.0, especially to the fact that Wicket 7.0
requires Java 7.0.
We're few weeks before release. *Is somehow possible to backport this
improvement to Wicket 6.x line?* Because this isn't good framework behaviour at
all,
if framework needs to recreate page it always has to be with page parameters if
there were any...
"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!"
Well, I'd expect that when I do redirect to another page then framework won't
care about the old page...*I'm redirecting, after all*... Martin debug the
attached myproject.zip.
Ajax timer or slowly processed ajax (it doesn't matter) running in old page
pushes out the newly created page when you do redirect with
PageNumberEvictionStrategy(1)...:-( I'd expect that when I do redirect with
PageNumberEvictionStrategy(1) then I will have just actual page in store...
Howto workaround this:
Right now, I can't think of any better solution then have two pages in store /
per browser tab. Or Martin can you provide me better one?
It's great that stateless ajax will create fresh page on each request, but if
it will be without page params then I can't use it.
> 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)
