This content has been marked as final.
Show 4 replies
-
1. Re: Thread-safety
nickarls Feb 8, 2010 8:05 PM (in response to romanb)The spec only speaks of serializing access to the conversation scope. I assume the same will be done for Seam 3 with (hopefully) portable extensions/filters/other magic.
-
2. Re: Thread-safety
asookazian Feb 8, 2010 9:50 PM (in response to romanb)
Seam will serialize concurrent requests made to CONVERSATION scope or SESSION scoped beans.Where did you find/see the above quote? I was under the impression that for Seam 2.x, serialization for concurrent requests are limited to CONVERSATION scope only...
Seam serializes access to the same conversation and will abort the request if it has to wait too long to get a lock on the conversation. -
3. Re: Thread-safety
nickarls Feb 8, 2010 10:50 PM (in response to romanb)4.1.10 of 2.2.0 docs:
Seam serializes requests to session scope session beans and JavaBeans by default (and detects and breaks any deadlocks that occur).
and 4.2.4
Concurrent requests to session-scoped JavaBeans are always serialized by Seam.
-
4. Re: Thread-safety
gavin.king Feb 17, 2010 4:41 PM (in response to romanb)You're right, the example code could probably do with a couple of synchronized modifiers.