[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-164) Kill all conversations

Tue Sep 30 22:13:24 EDT 2008

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

Srinivasan Raguraman updated JBSEAM-164:
----------------------------------------

    Attachment: kill-all-other-conversations.diff

Surprisingly, I have also worked on the same issue over the last two days. I have worked on this mostly based on the discussion on these thread:

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78766&postdays=0&postorder=asc&start=0

The other patch that posted just before looks good. I am not apposing it here, but just providing an alternate implementation for the seam committers to chose from. Or this may be additional way to achieve the same. Also this implementation differs from the last one, so I thought it will be good to submit it.

It takes the same approach as like time out of conversation, so the killed conversation will get notified with time-out events. This also takes care of the cases like, calling Conversation.killAllOthers() when there is a nested conversation is progress, or when called from a new or promoted conversation within @Begin. Added couple of test cases for it, and tested it with nested booking sample (changes made to nested booking is not attached here, as it will change the semantics of the original example)

Thanks

> Kill all conversations
> ----------------------
>
>                 Key: JBSEAM-164
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-164
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Core
>            Reporter: Gavin King
>             Fix For: The future
>
>         Attachments: kill-all-other-conversations.diff, seam-endall-patch-v1.diff
>
>
> Users want an operation to kill all conversations, and they want that to happen in the same action as beginning a new conversation.

-- 
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