I think that can be done on a framework level with optional parameter
or annotation such as:
@Persist("lazy-thread-safe-session")
that locks in the beginning of the request and unlocks in the end.
However I don't think it's a priority feature.
As for me it's enough to just put reminder to "Persistent State"
article. Warning like
"Remember that developer has the responsibility for threadsafe access
to the session objects. See Servlet 2.5 spec "
BTW Spring has such feature:
"Unfortunately, there's no option in the servlet specification to say
"force requests on the same session to be serialized." However, the
SpringMVC framework offers a way to ask for this, and the approach can
be reimplemented in other frameworks easily. The base class for
SpringMVC controllers, AbstractController, provides a boolean variable
synchronizeOnSession; when this is set, it will use a lock to ensure
that only one request on a session executes concurrently."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
