[cdi-dev] [JBoss JIRA] (CDI-370) Expand @RequestScoped and @SessionScoped to account for WebSocket

[Romain Manni-Bucau (JIRA)]

    [ https://issues.jboss.org/browse/CDI-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772615#comment-12772615 ] 

Romain Manni-Bucau commented on CDI-370:
----------------------------------------

Guys, this is a real issue of CDI.

RequestScoped => http request (+ few cases). So it means if you need a clean bean by thread (for thread safety for instance) you'll use it but your code will not be usable in a context without web front.
                
> Expand @RequestScoped and @SessionScoped to account for WebSocket
> -----------------------------------------------------------------
>
>                 Key: CDI-370
>                 URL: https://issues.jboss.org/browse/CDI-370
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>            Reporter: Joseph Snyder
>
> We've been testing injection into a WebSocket endpoint.
> @ReqestScoped objects are usable within the @OnOpen callback. This is because this object is executed within a valid request scope.
> However if you try to use the injected object from within the @OnMessage callback you get a Weld error:
> SEVERE:   org.jboss.weld.context.ContextNotActiveException:
> WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
> Can the definition of when @RequestScoped is active be expanded to include a WebSocket @OnMessage callback?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira