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 certain frame and that was recognized to look like a back-button request. I managed to change this and use setResponsePage now. Thanks for help! Chris -- View this message in context: http://www.nabble.com/Page-cache---page-pool-tf3213152.html#a8964047 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
