On Tue, 23 Nov 2010 12:30:42 -0200, Moritz Gmelin <moritz.gme...@gmx.de>
wrote:
Hi,
Hi!
Is this a design problem with my application that multple threads can
access the sessionstateobject at the same time and thus break its
uniqueness or is it tapestrys fault that it does not prevent it from
breaking?
It's not Tapestry's nor the servlet container to handle concurrency on
session objects. I suggest you to create a service that synchronizes
access to your SSO and use it instead of using @SessionState and
ApplicationStateManger directly. Another option is to decorate or override
ApplicationStateManager to add thread syncronization to them.
--
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
