a session object is created for every request, stateless or not. for stateless requests the session object is not put into the permanent session store (httpsession usually) - that is the difference.
-igor On Thu, Mar 19, 2009 at 4:38 AM, James Carman <[email protected]> wrote: > Wicket won't use a session unless it needs to. Are your pages stateless? > > On Mar 19, 2009 7:17 AM, "Edwin Ansicodd" <[email protected]> wrote: > > > There is an @Override annotation on the method and it does compile and > deploy. > > It seems almost as if the app processes each page request as a request and > not as part of a session. Is there something I have to set so wicket treats > requests as part of a session and not on a request by request basis? > > James Carman-3 wrote: > > On Wed, Mar 18, 2009 at 3:49 PM, Edwin Ansicodd > <[email protected]... > >> --------------------------------------------------------------------- > To > unsubscribe, e-mail: us... > View this message in context: > http://www.nabble.com/newSession%28%29-not-being-called-tp22584600p22598107.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]
