28.4. Seam-managed persistence contexts
http://docs.jboss.org/seam/3/latest/reference/en-US/html_single/

On Mon, Mar 5, 2012 at 10:02 AM, Rohit Kelapure <[email protected]> wrote:
>
> For SEAM 3 the most pertinent information in the defect is this ....
>
> Seam uses @ConversationScoped scope to manage his extended persistenceContext 
> which is one of the most convenient features.
>
> I will do some research and find out how they are using @ConversationScoped
> and if there is a sample application that illustrates this issue.
>
> -cheers,
> Rohit
>
>
>
> On Mon, Mar 5, 2012 at 9:43 AM, Mark Struberg (Commented) (JIRA) 
> <[email protected]> wrote:
>>
>>
>>    [ 
>> https://issues.apache.org/jira/browse/OWB-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222377#comment-13222377
>>  ]
>>
>> Mark Struberg commented on OWB-626:
>> -----------------------------------
>>
>> For DeltaSpike and CODI I can guarantee that this is not needed. As for 
>> Seam3: do you have any forum references or other links for me? We might 
>> reach out to JBoss to fix this in Seam3.
>>
>> > 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
>>
>>
>

Reply via email to