You should not need to do anything in Tapestry to disable sessions. If you are not using them, they should not be created. I have confirmed this in my own app.
On Oct 5, 2013, at 2:05 PM, Robert Hailey wrote: > > Greetings, all! > > I've nearly completed a really small service, and (as far as I know and have > written) it does not use session persistence in any way. > > Contrawise, I notice in testing that the JSESSIONID cookie is *still* being > sent to the browser under normal operations. > > Is there some way (outside of the containers configuration) that I can > disable sessions altogether? > > I notice, for example, that there is a ClusteredSessionImpl... can I easily > swap-in a NullSessionImpl ??? > > Thanks in advance! > > -- > Robert Hailey > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
