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 > but if you keep a refence to those pages and resuse them that is not a > problem > I have a common WebPage class that invokes something like PageCache.get().cache(this); The PageCache class does cachedPageMap.put(page.getPageClass(), page); The menu bar checks PageCache.get().pageFor(PageA.class), which checks the cachedPageMap for a page instance. If the result is not null, the page is displayed, otherwise a new page is created. 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). That happens in PageMap.access(), the comment there says: "Pop entries to reveal that version at top of stack because the user used the back button" (Page has still the same version and id...) Is there a way to tell wicket, that the back-button hasn't been used? Btw, I'm using wicket 1.2.4. Chris -- View this message in context: http://www.nabble.com/Page-cache---page-pool-tf3213152.html#a8923908 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
