Creating a nested conversation does not create a new convers

nagypalg Sep 21, 2007 2:57 AM

Hi,

I was a little surprised that creating a nested conversation (@Begin(nested=true)) does not necessary mean that you create a new instance of a conversation scoped bean. If the conversation scoped bean Foo already exists in one of the parent conversations of the current nested conversation, this bean is reused. I.e., changing the state of the bean in the nested conversation will have effects also in the parent conversation(s), after the nested conversation has ended. I tested it with Seam 2 CR1.

Is it the intended, long-term behavior or a bug? If it is intended, are there any best practices to have a different instance (or at least different state) of the same Foo bean in nested conversations?

--
Gabor

1. Re: Creating a nested conversation does not create a new con

stephen.friedrich Sep 21, 2007 3:20 AM (in response to nagypalg)

RT*M
6.2 Nested Conversation:

Usually, if a component exists in a parent conversation of the current nested conversation, the nested conversation
will use the same instance. Occasionally, it is useful to have a different instance in each nested conversation,
so that the component instance that exists in the parent conversation is invisible to its child conversations.
You can achieve this behavior by annotating the component @PerNestedConversation.
Actions
2. Re: Creating a nested conversation does not create a new con

nagypalg Sep 21, 2007 3:52 AM (in response to nagypalg)

Ups, sorry. Thanks anyway!
Actions

Go to original post