[
https://issues.apache.org/jira/browse/OWB-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221743#comment-13221743
]
Rohit Dilip Kelapure commented on OWB-626:
------------------------------------------
I attempted to reproduce the issue by modifying the JSF-2 sample. Added a
PhaseListener for RENDER_RESPONSE phase that accesses the current Conversation
scoped bean and retrieves conversation state. (See attached file). In all cases
I was able to access the correct current in-scope value of the conversation
scoped ConversationData bean.The conversation scope was active in
OWB626ConversationPhaseListener.afterPhase(PhaseEvent pe) method.
Thierry, can you please attach a testcase or sample code or let me know which
seam 3 example to run to reproduce this issue.
> Conversation Scope isn't accessible after RENDER_RESPONSE phase
> ---------------------------------------------------------------
>
> Key: OWB-626
> URL: https://issues.apache.org/jira/browse/OWB-626
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Reporter: Thierry Robin
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
> Attachments: OWB626ConversationPhaseListener.java
>
>
> In CDI 1.0, the Conversation Scope is normaly accessible from after
> RESTORE_VIEW phase in JSF, to the end of the Response.
> But It's not the case during the after phase(RENDER_RESPONSE) of any
> PhaseListener implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
