[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3467) Add conversation restart functionality

asookazian (JIRA) jira-events at lists.jboss.org
Sat Sep 27 11:57:30 EDT 2008


Add conversation restart functionality
--------------------------------------

                 Key: JBSEAM-3467
                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3467
             Project: Seam
          Issue Type: Feature Request
          Components: Core
    Affects Versions: 2.0.2.SP1
         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

        



More information about the seam-issues mailing list