[
http://jira.jboss.com/jira/browse/JBSEAM-1383?page=comments#action_12400699 ]
Nicklas Karlsson commented on JBSEAM-1383:
------------------------------------------
One possible usecase could be some sort of "application transaction" where you
fork the conversation and "rollback" just means to discard the fork and resume
where you split off...
Add conversation propogation="clone" ability
--------------------------------------------
Key: JBSEAM-1383
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1383
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
I think the ability to clone a conversation would be useful.
Currently if I have an s:link and I do an "open in new window" on that link I
now have 2 windows linked to the same conversation which may produce undesirable side
effects to the user.
So the idea is with s:link or other "GET" types of requests where the user
might be inclined to do an "Open in new Window" type of operation we add the
ability to clone the conversation when executed. If applied to an s:link the conversation
would always be cloned when that link is executed. That way if the user did do an
"Open in new window" each window would have 2 independent conversations.
This would obviously have the side effect of an orphaned conversation if the user
didn't do an "open in new window or tab" so the user would have to weigh the
cost of creating orphaned conversations against maintaining the Conversation per window
type of semantics this feature would provide.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira