If there currently is no session it won't create one - auto creating a session is undesirable in many cases - e.g. when serving up a static resource.
>-----Original Message----- >From: Raul [mailto:[email protected]] >Sent: Friday, 25 January 2013 6:08 AM >To: [email protected] >Subject: ThreadContext.getSession(); return null in wicket 6.5.0 > > >Hi, in my application I use ThreadContext.getSession () to get the session, >and works well in wicket 6.4.0, upgrade to 6.5.0 but returns null, what is >due? > > > >-- >View this message in context: http://apache- >wicket.1842946.n4.nabble.com/ThreadContext-getSession-return-null-in- >wicket-6-5-0-tp4655741.html >Sent from the Users forum 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]
