Thanks igor, the reason i asked so was because i am seeing this wierd behavior on oc4j where even if i just do a redirect to an external app in my CustomWebWession (on the very first request to my wicket app) without even rendering any wicket page, i see a jsessionId cookie being set..
igor.vaynberg wrote: > > correct > > you can also bind the session manually by calling bind() > > -igor > > > On Mon, Apr 28, 2008 at 10:46 PM, mfs <[EMAIL PROTECTED]> wrote: >> >> Correct me if i am wrong.. >> >> - Wicket creates a permanent session only when a stateful page is >> rendered. >> And it is at this time when the wicket session is bind with the >> http-session, and hence a jsessionID is generated by the servlet >> container >> and set as a cookie in the response. >> >> - On the contrary, for stateless-pages wicket does create temporary >> session >> which i believe are alive only for that particular request cycle...and >> is >> not bind with the httpsession in any way. ? >> >> Thanks in advance. >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/About-Wicket-Session-life-cycle-tp16953686p16953686.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] > > > -- View this message in context: http://www.nabble.com/About-Wicket-Session-life-cycle-tp16953686p16953916.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]
