On Fri, 28 May 2010 00:31:18 -0300, Paul Stanton <p...@mapshed.com.au>
wrote:
Surely this is a bug in t5 ...
I disagree. HTTP is purely stateless. Session keeping is the container's
(server) responsibility, not Tapestry's. With cookies disabled, the only
way to find out what is the session is appending the ;jsessionid=xxx
string to the URLs. This is done by HttpServletResponde.encodeURL(String
url), which is indirectly invoked for every single link generated by
Tapestry.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
