Wicket will read the page *instance* from the page store, and then process the render phase of the request cycle using that instance. If you use LoadableDetachableModel (or similar models that refresh their contents) you get a refreshed page.
Martijn On Thu, Sep 9, 2010 at 10:26 PM, Mike Dee <mdichiapp...@cardeatech.com> wrote: > > Does that mean if the back button is used to go back to a URL like this: > > http://myurl/myapp/?wicket:interface=:3:::: > > and the SHIFT-REFRESH button is used (hard refresh), that Wicket will pull > the page out of its cache rather than calling the app to regenerate the > page? > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Demystifying-page-serialization-tp2533538p2533548.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
