[jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-1943) Support for destroying the entire ConversationStack

Pete Muir (JIRA) jira-events at lists.jboss.org
Fri Sep 19 07:46:21 EDT 2008


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

Pete Muir reopened JBSEAM-1943:
-------------------------------



We should move the endRoot logic into a convenience method on Manager.

> Support for destroying the entire ConversationStack
> ---------------------------------------------------
>
>                 Key: JBSEAM-1943
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1943
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Jacob Orshalick
>            Assignee: Jacob Orshalick
>             Fix For: 2.1.0.CR1
>
>         Attachments: JBSEAM-1943-ConversationControl-v1.patch, JBSEAM-1943-ConversationInterceptor-v1.patch, JBSEAM-1943-End-v1.patch, JBSEAM-1943-EndTask-v1.patch, JBSEAM-1943-HotelBookingAction-v1.patch, JBSEAM-1943-pages-2.0-dtd-v1.patch, JBSEAM-1943-pages-2.0-xsd-v1.patch
>
>
> There are situations where I would like to be able to destroy the entire conversation stack if a particular action occurs (say a user cancels everything during a nested conversation, an exception occurs during a nested conversation, etc). I am currently accomplishing this through the following:
> private void endRootConversation() {
> 	Conversation conversation = Conversation.instance();
> 	
> 	while(conversation.isNested()) {
> 		conversation.root();
> 	}
> 		
> 	conversation.endBeforeRedirect();
> }
> I would prefer to say something like @End(root=true) or specifying conversationPropogation="endRoot".  Similar discussions on the forum are:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112414&postdays=0&postorder=asc&start=10
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118936&postdays=0&postorder=asc&start=20

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