[jira] Resolved: (ORCHESTRA-19) refactor conversationContext to allow nested conversationContext

["Simon Kitching (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/ORCHESTRA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Kitching resolved ORCHESTRA-19.
-------------------------------------

    Resolution: Fixed

Trunk now has the ability to create nested conversations and swap between them. So closing this as fixed.

> refactor conversationContext to allow nested conversationContext
> ----------------------------------------------------------------
>
>                 Key: ORCHESTRA-19
>                 URL: https://issues.apache.org/jira/browse/ORCHESTRA-19
>             Project: MyFaces Orchestra
>          Issue Type: Improvement
>          Components: Conversation
>            Reporter: Mario Ivankovits
>
> The conversationContext should be enhanced to allow nested conversationContext which is a requirement for dialog/flow implementations to separate the conversations for different flows.
> The new conversationContext should be able to handle:
> * a conversation context per windows
> * multiple named conversationContexts
> * a stack of conversationContexts to fulfill the requirement a dialog framework has with its subflows
> Technically this might all be the same conversationContext implementation .... probably.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.