The use of Session.bind() has resolved my problem. If I have a bookmarkable login page, then, I suppose I should bind the session before storing the user's data to the session?
On Sat, Aug 23, 2008 at 9:15 PM, brian.diekelman <[EMAIL PROTECTED]> wrote: > > It depends on the situation and your logging setup. Do this to verify: > > - First put a logging statement in WebApplication.newSession(), not > MySession.get() > > - Open a new browser window and go to your 'verify' bookmarkable page. You > should see a new session created on each refresh > > - Now put 'getSession().bind()' somewhere in your page constructor. > > - Cycle/redeploy the app and go to the 'verify' bookmarkable page. You > should only see one session created, and it should reuse that session on > each refresh. > > > If any of the above didn't happen as described, that's what I would call > unexpected behavior. Otherwise, what was the expected vs actual behavior? > > -- > View this message in context: > http://www.nabble.com/Session-creation-tp19123581p19127645.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
