]
Antoine Sabot-Durand reassigned CDI-380:
----------------------------------------
Assignee: Antoine Sabot-Durand
Clarify SessionScoped
---------------------
Key: CDI-380
URL:
https://issues.jboss.org/browse/CDI-380
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Joseph Snyder
Assignee: Antoine Sabot-Durand
Priority: Minor
Labels: CDI_api_chge, CDI_spec_chge, Ready_to_fix
Fix For: 1.2 Proposed
The javadocs say:
The request context is destroyed:
- at the end of the servlet request, after the service() method, all
doFilter() methods, and all requestDestroyed() and onComplete()
notifications return,
...
The session context is destroyed when the HTTPSession times out, after all
HttpSessionListeners have been called, and at the very end of any request in
which invalidate() was called, after all filters and ServletRequestListeners
have been called.
Those definitions are different.
The session context rule seems to be a combination of "or" items that
include some "and" items. It's difficult to parse. It would be clearer
if it was written as a list. And, like request scoped, it would be clearer
if it described when the session scope/context is created.
--
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: