It seems that you homepage is stateless, wicket does not create a session for stateless pages to preserve server resources. You can force wicket to create a session for you by calling Session.get().bind() in your constructor (or any other place that is executed during a requestcycle).
Maurice On Sat, Jun 14, 2008 at 9:48 PM, Stefan Simik <[EMAIL PROTECTED]> wrote: > > Hi boys, > > I would like to ask, how can I force creation of HTTP session > when first request comes to server. > > I have this problem: > 1. user requests home page (wicket session is created) for example: > www.server.com/app > 2. I set some data into the wicket session > 3. server responds with redirect to some random bookmarkable page: > www.server.com/app/pc > > 4. At the next request - HERE IS THE PROBLEM - there are no previously > stored data in the session. > > At the second and next requests, there is no problem with session. What I > save into the session, > I can find in later requests. The problem is in the first roundtrip, so it > seems, that > the real HTTP session is not created in the first request. > > Where should I look for some solution please? > -- > View this message in context: > http://www.nabble.com/HTTP-Session-creating-at-home-page-tp17843162p17843162.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]
