[cdi-dev] [JBoss JIRA] (CDI-379) Clarify life cycle of RequestScoped

[Antoine Sabot-Durand (JIRA)]

     [ https://issues.jboss.org/browse/CDI-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Sabot-Durand closed CDI-379.
------------------------------------

    Resolution: Rejected


This task was examined during 12/02/2013 EG meeting (Hangout).
CDI spec cannot tell how other spec use built-in scopes.
So it's the work of each specification to give information about validity and activation of @RequestScoped and others.
                
> Clarify life cycle of RequestScoped
> -----------------------------------
>
>                 Key: CDI-379
>                 URL: https://issues.jboss.org/browse/CDI-379
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Joseph Snyder
>            Priority: Minor
>
> This is one of the areas where the CDI spec could be clearer.  It defines
> the points where "some" request scope is active, and where "some" request
> scope is destroyed, but it doesn't clearly state what the span of a particular
> request context is.  You sort of have to work backwards and figure it out.
> Update the spec to indicate when a particular request scope is
> created, what operations it's active during, and when it's destroyed.

--
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