That's from Tapestry side. Maybe you should take a look at your servlet
container documentation to know whether you can disable sessions there.
On Sat, 05 Oct 2013 15:30:50 -0300, Thiago H de Paula Figueiredo
<thiag...@gmail.com> wrote:
On Sat, 05 Oct 2013 15:05:24 -0300, Robert Hailey <rhai...@allogy.com>
wrote:
Greetings, all!
Hi!
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 think you can override or decorate the TapestrySessionFactory service
so the getSession(boolean) method returns a Session implementation that
doesn't actually stores anything (your NullSessionImpl). This solution
is for 5.3 and later and I haven't tested it.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
