see wicket-dev-utils, there is a stateless checker there that can help you.
wicket's session object is created on every request, but while the app is not stateful it is not persisted/put into httpsession. so you will always have a session object during a wicket request. there is page.ispagestateless() that will tell you if the page is stateless or not after render. -igor On Wed, May 20, 2009 at 6:49 AM, adrien le roy <[email protected]> wrote: > Hello, > > I am a little bit confuse about about how to test if a session have > been created in a Panel > I was using Session.get() but it is creating session if it don't exists. > Regarding stateless page, how to test if a page is stateless ? > If I have understood well, a page is considered statefull when a > session is created during requestcycle? > > Thanks > > --------------------------------------------------------------------- > 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]
