[
https://issues.apache.org/jira/browse/ORCHESTRA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586009#action_12586009
]
imario edited comment on ORCHESTRA-19 at 4/5/08 8:01 AM:
-------------------------------------------------------------------
First draft committed. Most noteworthy are startConversationContext and
activateConversationContext which allows one to start new conversation contexts
as child of the current one. One has to take care about to call
activateConversationContext() at the right time.
Unhappily I had to break binary compatibility of the conversationContext class.
This might mean that we are on the way to Orchestra 2. Though, if one did not
customize Orchestra in that area (which is highly unlikely that one did) it is
still a drop-in upgrade.
was (Author: imario):
First draft committed. Most noteworthy are startConversationContext and
activateConversationContext which allows one to start new conversation contexts
as child of the current one. One has to take care about to call
activateConversationContext() at the right time.
Unhappily I had to break binary compatibility of the conversationContext class.
This might mean that we are on the way to Orchestra 2. Though, I one did not
customize Orchestra in that area (which is highly unlikely that one did) it is
still a drop-in upgrade.
> 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.
