[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1416) Make it clear in the documentation that Session scope concurrency is only handled when interception is enabled

Thu Jun 7 11:13:14 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBSEAM-1416?page=comments#action_12364523 ] 

Mike Quilleash commented on JBSEAM-1416:
----------------------------------------

In fact it should probably fail on startup if interception is disabled and @Synchronized is specified.  It should also probably at least warn, and maybe fail, if interception is disabled for some phases (AFTER_RESTORE_VIEW etc).

> Make it clear in the documentation that Session scope concurrency is only handled when interception is enabled
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-1416
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1416
>             Project: JBoss Seam
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 1.2.1.GA
>         Environment: Any
>            Reporter: Mike Quilleash
>
> The concurrency section of the documentation says that seam automatically makes session scoped components threadsafe. 
> Quote:
> Since the session context is multithreaded, and often contains volatile state, session scope components are always protected by Seam from concurrent access.
> However the implementation of this uses an interceptor so components that disable interception (InterceptionType.NEVER) will not benefit from this and threadsafety will have to be built into the component itself.  This should be documented as the above states that they are ALWAYS protected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira