[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3385) Destroying one conversation from within another

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Wed Nov 5 21:57:21 EST 2008


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

Shane Bryzak updated JBSEAM-3385:
---------------------------------

    Fix Version/s: 2.1.2.CR1
                       (was: 2.1.1.CR1)


> Destroying one conversation from within another
> -----------------------------------------------
>
>                 Key: JBSEAM-3385
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3385
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0.A1
>         Environment: JBoss 4.2.3.GA
>            Reporter: Bernard Labno
>             Fix For: 2.1.2.CR1
>
>         Attachments: EndNaturalConversation.zip
>
>
> There is a problem with destroying conversation via ConversationEntry.destroy().
> In ConversationEntry :
> public void destroy() 
> {
>    boolean success = Manager.instance().switchConversation( getId() );
>    if (success) Manager.instance().endConversation(false);
> }
> After this method the conversation id is wrong ! We could have destroy one conversation from another and guess which conversation's id will appear if we try to render it ? The removed conversation's ! We just removed one conversation and got kicked out of another.

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

        



More information about the seam-issues mailing list