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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087049#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...