[
https://issues.apache.org/jira/browse/ORCHESTRA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585651#action_12585651
]
Mario Ivankovits commented on ORCHESTRA-19:
-------------------------------------------
The conversationContext api needs to be enhanced to get access to specific
types of conversationContext.
* byId (already there)
* byName (user definable name)
* byType (e.g. find the one responsible for the window data)
> 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.
