okay, suit yourself, but this is the normal/expected use case for wicket detachable models, which are the preferred route to go. i think you will find other options less workable.
mfs wrote: > > we might opt for this eventually, but trying to utilize/serve-the-purpose > for now with what wicket offers... > > > > Jonathan Locke wrote: >> >> >> normally you don't hit the db on refresh. you hit a fast local db cache. >> >> >> mfs wrote: >>> >>> Guys, >>> >>> Firstly, Is that a right understanding that doing a browser-refresh of >>> the page would result in a new instance of the page being created >>> everytime and similarly a new model instance would be binded to the >>> page. >>> >>> Is there a way one can use the same version of the page/model (which >>> wicket kept in the session) when the page was rendered the first time.. >>> >>> I would want to avoid a hit to the database on refresh (since my model >>> construction requires so) >>> >> >> > > -- View this message in context: http://www.nabble.com/Load-serialized-%28or-in-session%29-page-model-on-refresh..-tp17170105p17178970.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
