[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1609) Nested conversations - potential bug in Manager.beginNestedConversation

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1609?page=all ]

Gavin King updated JBSEAM-1609:
-------------------------------

    Fix Version/s: 2.0.0.CR1
         Assignee: Gavin King
         Priority: Blocker  (was: Major)

> Nested conversations - potential bug in Manager.beginNestedConversation
> -----------------------------------------------------------------------
>
>                 Key: JBSEAM-1609
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1609
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>            Reporter: Wolfgang Schwendt
>         Assigned To: Gavin King
>            Priority: Blocker
>             Fix For: 2.0.0.CR1
>
>
> See thread in JBoss Forum
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112414
> very short summary of above thread:
> if @Begin(nested=true) is encountered and there is no long-running conversation in progress, Seam creates a new nested
> conversation which is not a long-running, but instead a temporary conversation.    
> This behavior does not look like intended, given that  beginNestedConversation() of  org.jboss.seam.core.Manager contains a guard that tries to check whether a long-running conversation is in progress.  The potential bug is that this guard condition is too weak, as described in JBoss forum thread mentioned above.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira