[
https://issues.jboss.org/browse/CDI-370?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-370:
------------------------------------------
It’s the responsibility of Websocket spec to implement these scopes. We should ensure they
take the point before closing the ticket.
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
Assignee: Antoine Sabot-Durand
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