[
https://jira.jboss.org/jira/browse/JBSEAM-164?page=com.atlassian.jira.plu...
]
Stuart Douglas commented on JBSEAM-164:
---------------------------------------
The patches are a fair bit different in what they accomplish. Mine kills all
conversations, including the current one, and creates a new temporary conversation
context, which can be promoted to long running if so desired.
I do not think it is a good idea to send out conversationTimeout events when using
killingAllOthers, as this is not a timeout event. As the event is explicitly triggered by
the developer, I would just let them explicitly send out any events that they may want, or
else send out some kind of conversationKilled event.
Stuart
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