[
https://issues.apache.org/jira/browse/ORCHESTRA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585944#action_12585944
]
Mario Ivankovits commented on ORCHESTRA-20:
-------------------------------------------
Committed a fix for that too. Unfortunately this introduces a small binary
incompatibility if one implemented a custom scope.
In AbstractSpringOrchestraScope:
protected String getConversationNameForBean(String beanName)
has been changed to
public String getConversationNameForBean(String beanName)
> single conversation
> -------------------
>
> Key: ORCHESTRA-20
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-20
> Project: MyFaces Orchestra
> Issue Type: Improvement
> Components: Conversation
> Reporter: Mario Ivankovits
>
> Create an implementation of a "single conversation".
> A dialog/flow framework will create new conversationContexts instead of
> direct conversations.
> While you still will be able to use conversation.manual or
> conversation.access it makes sense to also provide a conversation.single
> implementation which shares the lifetime of the conversationContext (managed
> by the dialog framework) and has only one (single) persistence context.
> Still, mixing the various conversation implementations is possible.
> Probably Conversation.getCurrentInstance() outside of a conversation will
> return this single conversation if it exists within the current
> conversationContext.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
