[weld-issues] [JBoss JIRA] Commented: (WELD-229) RequestScoped Bean instance is stored in the context after its deactivation/activation

Fri Oct 23 11:37:05 EDT 2009

    [ https://jira.jboss.org/jira/browse/WELD-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12491252#action_12491252 ] 

Jozef Hartinger commented on WELD-229:
--------------------------------------

This works however in the servlet environment org.jboss.jsr299.tck.tests.lookup.clientProxy.incontainer.ClientProxyTest.testInvocationIsProcessedOnCurrentInstance() so I guess either it is the issue only in the standalone mode or using setContextInactive/setContextActive from AbstractJSR299Test is not a correct way of simulating new request.

> RequestScoped Bean instance is stored in the context after its deactivation/activation
> --------------------------------------------------------------------------------------
>
>                 Key: WELD-229
>                 URL: https://jira.jboss.org/jira/browse/WELD-229
>             Project: Weld
>          Issue Type: Bug
>          Components: Scopes & Contexts
>    Affects Versions: 1.0.0.CR1
>            Reporter: Jozef Hartinger
>            Assignee: David Allen
>             Fix For: 1.0.0.CR2
>
>
> org.jboss.jsr299.tck.tests.lookup.clientProxy.ClientProxyTest.testInvocationIsProcessedOnCurrentInstance()

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