Thanks for the answer.
I have tried to define a name for my conversation but did not succeed. All
I found in the documentation was the hint of some hidden id on page specs.
"Orchestra also provides the concept of a "conversation context", which
holds a set of named conversations. A "separateConversationContext" JSF
component creates a new context. When this is a parent of any command
component (eg a commandLink) then a new conversation context is
automatically created when that command is executed. This allows multiple
windows to access the same site while having completely independent sets of
objects that are of "conversation scope". A hidden "id" emitted into pages
specifies what the current conversation context is, ensuring the new
windows "sticks" with its associated conversation context."
Can you please describe how I can define names for my conversations and how
to force my beans to use a spezially named conversation ?
THX
AG WW
simon
<[EMAIL PROTECTED]
hello.at> To
MyFaces Discussion
06.02.2008 08:16 <[email protected]>
cc
Please respond to Subject
"MyFaces Re: How can I have more than one
Discussion" bean in an orchestra conversation
<[EMAIL PROTECTED]
ache.org>
On Wed, 2008-02-06 at 00:54 +0100, Wolfgang Wagner wrote:
>
> In my application context i have defined multiple beans with
> scope="conversation.manual"
> When calling Conversation.getCurrentInstance().invalidate() in an action
> method of one of these beans only that bean gets destroyed.
>
> It seems as if there is one conversation object for each of my
conversation
> scoped beans.
> I have expected that newly created beans that are are under conversation
> scope join automatically an already running conversation, and get
destroyed
> whenever the conversation gets destroyed.
>
>
> Is there a way to have multiple objects in one conversation ??
Yep. Each conversation has a *name*. If you do not specify a name for a
conversation, then conversationName=beanName.
If two beans are assigned to a conversation with the same name, then
invalidating that conversation invalidates both beans.
Regards, Simon
