[cdi-dev] [JBoss JIRA] Closed: (CDI-148) Conversation Scope should be as available as Request Scope (Ubiquitous), and not tied to JSF

Tue Sep 6 10:58:26 EDT 2011

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

Pete Muir closed CDI-148.
-------------------------

    Fix Version/s:     (was: 1.1 (Proposed))
       Resolution: Duplicate Issue


> Conversation Scope should be as available as Request Scope (Ubiquitous), and not tied to JSF
> --------------------------------------------------------------------------------------------
>
>                 Key: CDI-148
>                 URL: https://issues.jboss.org/browse/CDI-148
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Contexts
>    Affects Versions: 1.0
>            Reporter: Lincoln Baxter III
>
> In CDI 1.0, the Conversation Scope has extremely limited availability. It is accessible from *after* RESTORE_VIEW phase in JSF, to the end of the Response, but this is extremely limiting, and in fact does not even address all use-cases within JSF. 
> For instance:
>  * User has custom PhaseListener for *Before* RESTORE_VIEW phase, or user has custom PhaseListener that invokes before ConversationPhaseListener.
>  * In said PhaseListener, user attempts to access a ConversationScoped bean.
>  * ContextNotActiveException results, even though there may be a valid CID in the Request URL
> Example 2:
>  * User attempts to access ConversationScope outside of the JSF lifecycle (Via EL in a Servlet or ServletFilter, for instance.)
>  * ContextNotActiveException results, this just doesn't work!
> There is no reason why the ConversationScope should be any less available than the RequestScope, since both depend on the same underlying context objects. (Request, Session, etc)
> ConversationScope should be ubiquitous in the Servlet Container Request/Response lifecycle. This will greatly improve ability to use CDI in view/web frameworks other than JSF.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira