[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1982) Improved documentation for Nested Conversations

Jacob Orshalick (JIRA) jira-events at lists.jboss.org
Tue Oct 14 22:41:20 EDT 2008


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

Jacob Orshalick closed JBSEAM-1982.
-----------------------------------

    Resolution: Duplicate Issue


> Improved documentation for Nested Conversations
> -----------------------------------------------
>
>                 Key: JBSEAM-1982
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1982
>             Project: Seam
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 2.0.0.CR1
>            Reporter: Jacob Orshalick
>
> Nested conversations have been discussed at length on several occasions on the forum.  The documentation states:
> "A conversation may be thought of as a continuable state. Nested conversations allow the application to capture a consistent continuable state at various points in a user interaction, thus insuring truly correct behavior in the face of backbuttoning and workspace management."
> This gives the impression of use of nested conversations to achieve a continuation server approach.  This approach is possible and is described at the forum reference, but it seems that most developers use nested conversations for sub-flows ending the conversation at the end of the sub-flow.  This does not allow back-buttoning to the sub-flow (which seems to be in conflict with the documentation above).
> (I will add a link to an article describing the continuation approach in a few weeks, perhaps it could serve as a patch)

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