[seam-dev] Fwd: [jbossseam-issues] [JBoss JIRA] Deleted: (JBSEAM-3467) Add conversation restart functionality

From: "Christian Bauer (JIRA)" <jira-events(a)lists.jboss.org&gt; Date: 29 September 2008 19:59:21 BST To: jbossseam-issues(a)lists.jboss.org Subject: [jbossseam-issues] [JBoss JIRA] Deleted: (JBSEAM-3467) Add conversation restart functionality [ https://jira.jboss.org/jira/browse/JBSEAM-3467?page=com.atlassian.jira.pl... ] Christian Bauer deleted JBSEAM-3467: ------------------------------------ > Add conversation restart functionality > -------------------------------------- > > Key: JBSEAM-3467 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3467 > Project: Seam > Issue Type: Feature Request > Environment: Windows Server 2003 > JBoss EAP 4.3.0.CP02_FP01 > JRockit 1.5 JVM > Reporter: asookazian > > need functionality that will restart conversation (via > endBeforeRirect() and begin() methods in Conversation API or > similar). suggested solution from JBoss dev sppt did not work (see > forum URL below). workaround was to create a private method in > SFSB that set instance variables to null and continue with existing > LRC. a more elegant solution is preferred (Seam ending current > LRC, creating new LRC and transferring state from old conversation > variables to new one via restart() api call). > Scenario: conversation begin demarcation is driven by selection of > a drop-down (h:selectOneMenu) value. when user selects the new > value the second time, the conversation should end and start a new > LRC. Solution from dev sppt did not work b/c the > endBeforeRedirect() method was being called in action binding > method for drop-down in SFSB and subsequently, in pages.xml, <begin- > conversation> was coded prior to redirect to same xhtml. > Result: after the JSF was re-rendered after 2nd drop-down > selection, the value in the drop-down was set to "select value" > which is the default value. It should have been set to the 2nd > selection. The reason this is happening is b/c the instance > variables are conversation-scoped (b/c the SFSB is conversation- > scoped) and thus are presumably no longer available to the second > LRC (which strangely enough is still showing the original cid in > the debug.seam page after refresh!) -- 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 _______________________________________________ seam-issues mailing list seam-issues(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-issues