1. use LDM or AbstractReadOnlyModel to load your data on PageA. i use LDMs to load almost all data and about the only time I don't use an LDM is during a wizard scenario, where the same object needs to be updated across request.
2. disable caching of the page so that the server is requested when the user hits the back button. on PageA, override onBeforeRender and put a breakpoint in it to make sure the page is getting called when you hit the back button. Wicket 1.4 and Wicket 1.5 have different ways of doing, but here is an example in Wicket 1.4 about what I'm referring to: http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ Rob -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Back-button-showing-a-page-with-stale-data-tp4233580p4233747.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
