Hi!
I think that the orchestra conversation (or conversationContext?) can
exist simultaneously; the problem is I cant switch between
conversation; I can do it manually;
Yep, but the main idea of the conversationContext is to allow to use
multiple windows.
So, if you wrap an outputLink within an ox:separateConversationContext
and the users click this link a new conversationContext will be created
and you use-case will work.
I cant see what we can do more here, what you would like to have (I
presume) is to being able to configure a group of beans and maintain
your own "conversationContext" just for this group of beans.
This is not easily possible.
Hmmm .... what you can do is to create your own scope implementation
based on the Orchestra one and prefix the conversation name with
something like "1_", "2_" etc based on an ThreadLocal maintained by your
app.
But that is way too complicated and you'll end up with scope
implementations per "use-case".
I'd propose to maintain a list of "open orders" and when you switch them
you'll simply invalidateAndRestart the conversation an init it again.
Means, simply solve this in your application.
Having conversations around open too long might result in invalid data
shown to the user .... Keep conversations as short as possible, at least
if they deal with persistent data. I use conversations in the end open
as long as the session, but they do not fetch something from the
database but just hold some state.
Ciao,
Mario
