[cdi-dev] [JBoss JIRA] (CDI-380) Clarify SessionScoped

[Jens Schumann (JIRA)]

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

Jens Schumann commented on CDI-380:
-----------------------------------

Copy & paste from CDI-379: As stated in CDI-370 I still believe the CDI spec is way to verbose regarding scopes and related APIs. I think it would be better to move most of the stuff to the related specs (servlet, ejb, ...) or even the Java EE umbrella.
                
> Clarify SessionScoped
> ---------------------
>
>                 Key: CDI-380
>                 URL: https://issues.jboss.org/browse/CDI-380
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Joseph Snyder
>            Priority: Minor
>
> 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: http://www.atlassian.com/software/jira