On Fri, 29 Oct 2010 12:14:18 -0200, Moritz Gmelin <moritz.gme...@gmx.de>
wrote:
Hi,
Hi!
It happened to me again that one of my RequestFilters was creating a
SessionStateObject. Which, when done for all assets of a page simply
fails at one point. Different Threads accessing different Assets in
parallel start to create new Sessions and thus the SSO gets lost.
What are you using to create the SSO and set it in the session?
Now one can resolve this by putting all RequestFilters that use the SSO
behind the StaticFile filter. But since it is not enforced by Tapestry,
other people might stumble over this.
Why don't you just set the SSO in page requests?
So that it would be OK to have multiple parts of the page be handled by
different threads using the same SSO?
Multiple parts of a page be handled by different threads? I'm not
following you. Rendering a given page is done by a single thread for a
given request.
--
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
