[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4460) <begin-conversation killPrevious="true"/>

[Wang Liyu (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12521861#action_12521861 ] 

Wang Liyu commented on JBSEAM-4460:
-----------------------------------

This is a really useful feature, currently I have to do the end before redirect trick, this is fine for a normal web app (non-ajax), things with a4j:include become very troublesome, seam page using a4j:include has to define with render, instead of redirect, and it doesn't release previous conversation, there is a way to manully release the previous conversation, but I was told that is not the thing you can do with Seam (I actually made it working), here is the link:

http://www.seamframework.org/Community/HowToEndAndBeginANewConversationWithOneSignleSlink

http://www.seamframework.org/Community/TheRenderTagDoesntTriggerEndconversationBeforeredirecttrue

http://www.seamframework.org/Community/EndconversationBeforeredirecttrueDoesntWorkWithRenderViewidTag

> <begin-conversation killPrevious="true"/>
> -----------------------------------------
>
>                 Key: JBSEAM-4460
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4460
>             Project: Seam
>          Issue Type: Feature Request
>    Affects Versions: 2.1.2.CR2, 2.1.2.GA, 2.2.0.CR1, 2.2.0.GA
>            Reporter: deanhiller
>
> Please please please add the ability to kill the previous conversation when starting a new one.  Nearly all seam code I have seen for starting a conversation would typically use this as this is typically the default that would be wanted(but does not yet exist).
> For backwards compatibility, keep the default false I guess, BUT have a property in components.xml or somewhere where developers can set previousKillDefaultValue="true" so the default will be true for all of my current begin conversation tags.  I have looked in my project and start 16 conversations in different places all of which want to kill off the previous conversation instead of a debug.xhtml page popping up (or in production, the "a bug has occurred in our software, we are sorry for the inconvenience".
> thanks,
> Dean

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