[
https://issues.apache.org/jira/browse/OWB-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135058#comment-13135058
]
Thierry Robin commented on OWB-626:
-----------------------------------
Thank you very much for your detailed response.
You're right "the extended persistence context is pretty questionable" ... for
standard uses. But we have (also) some little applications, non critical,
written in few weeks and which don't care about clustering, concurrency
modifications, and so on ..
For this kind of applications (and only this kind), we've decided to use the
Seam(2) managed persistence context (with it's restrictions) and we'll probably
do the same with Seam3.
So, the question isn't about extended persistence context rightness, but just
running seam3 with another CDI implementation.
btw, I'm going to take a look at CODI.
> 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.1.3
>
>
> 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
