Hi,
Johan Compagner wrote:
So if you show A the second time then yes B is dropped. But if you then do
setResponsePage(B) B is again pushed to the stack and should be able to
render fine.
I found out why this questions sounded so stupid to you: I used ajax to show
the cached page in a
Hi,
for our navigation bar, I want to use a page cache to resume editing the
latest page version. Wicket's page map acts like a stack, so opening
PageA,
PageB,
PageA,
leads to the expiration of the PageB instance. However I want to reuse the
cached/saved page instance of PageB (could be a
if you keep on to PageB in PageA and when you want to go back to PageB
then you can set that page as a response page. That should work fine
So just keep a reference in a map to the pages you want.
We do clear them from the pagemap when we encounter a backbutton
but if you keep a refence to those
Hi,
Johan Compagner wrote:
if you keep on to PageB in PageA and when you want to go back to PageB
then you can set that page as a response page. That should work fine
So just keep a reference in a map to the pages you want.
We do clear them from the pagemap when we encounter a backbutton
However if pageA, pageB, pageA, pageB is opened then I see a page expired
error page instead of the last pageB, because the second opening of pageA
(which uses the same instance as first time) looks like a back-button for
wicket and pageB drops out of the stack (and thus gets expired).
So if
