[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1774) org.jboss.seam.core.Contexts factories put *Context components into application scope

[Matt Drees (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-1774?page=comments#action_12372041 ] 
            
Matt Drees commented on JBSEAM-1774:
------------------------------------

Hmm.  I know at the very least in a SeamTest class with two @test methods when the second one evaluates #{sessionContext}, it gets a context backed by the MockHttpSession of the first @test method.  I've seen it happen, which was how I found this bug.

I haven't tried to duplicate it in a non-test environment, so you could be right, but I don't think so.  The SessionContext, eg, is a wrapper for externalContext.getSessionMap().  I don't think the underlying SessionMap can be replaced when a new user logs in.

> org.jboss.seam.core.Contexts factories put *Context components into application scope
> -------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-1774
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1774
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>         Environment: cvs
>            Reporter: Matt Drees
>         Assigned To: Pete Muir
>            Priority: Critical
>             Fix For: 2.0.0.CR1
>
>
> The factories in org.jboss.seam.core.Contexts do not specify the Stateless scope, so when calling #{sessionContext}, for example, it gets cached in the application scope. 

-- 
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