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

Bill Shannon (JIRA) jira-events at lists.jboss.org
Fri Dec 6 13:46:07 EST 2013

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

Bill Shannon commented on CDI-379:

There's two parts to this:

1. The existing uses of @RequestScoped need to be better specified.  Yes, that should
    probably be done in each spec that controls the scope, but until that can be done it
    would be helpful to do it in the CDI spec.
2. The definition of @RequestScoped needs to be generalized so that it's clear that
    other specs *can* define their own use of @RequestScoped, and that the use of
    @RequestScoped isn't limited to the cases currently defined by the CDI spec.
> 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

More information about the cdi-dev mailing list