-
1. Re: Question about Conversations and Stateful Bean Instances
pmuir Dec 4, 2006 6:06 PM (in response to ekusnitz)Have you checked on debug.seam that the conversation is actually ended?
Also are you sure you're not mistakenly calling the method on the superclass? Does it really need the @Name annotation? -
2. Re: Question about Conversations and Stateful Bean Instances
gavin.king Dec 5, 2006 7:45 AM (in response to ekusnitz)You are creating nested conversations. They will see the component from the outer conversation.
-
3. Re: Question about Conversations and Stateful Bean Instances
ekusnitz Dec 5, 2006 9:27 AM (in response to ekusnitz)1. For some reason, we haven't been able to get to the debug page since we updated to 1.1CR2 with Portal 2.4.1. Previously, however, we were not seeing any conversations on that page
2. There is no @Create method on the superclass. It probably does not need the @Name annotation (I didn't code this...). Is that a problem?
3. Most important, is the answer Yes, the @Create method should be called when a conversation is begun, or No, not with nested conversations, or other?
Thanks for your responses -
4. Re: Question about Conversations and Stateful Bean Instances
ekusnitz Dec 5, 2006 11:45 AM (in response to ekusnitz)As far as the ancestor having @Name, I think this is needed because we want to do bijection on some inherited fields. Is there another way to achieve this?
-
5. Re: Question about Conversations and Stateful Bean Instances
pmuir Dec 5, 2006 12:36 PM (in response to ekusnitz)If the superclass doesn't need to be bijected don't @Name it (Seam will work its way up the class hierachy bijecting where it sees @In).
@Create is only called when the bean is instantiated. Nothing to do with whether a conversation has been started. -
6. Re: Question about Conversations and Stateful Bean Instances
ekusnitz Dec 5, 2006 12:40 PM (in response to ekusnitz)Thanks for the info. So where is the state saved for multiple conversations on the same instance?
-
7. Re: Question about Conversations and Stateful Bean Instances
pmuir Dec 5, 2006 6:15 PM (in response to ekusnitz)Well the state is stored in the context (conversation, event, session etc). So, if your bean is conversation scoped, the state is stored in the conversation context and there will only be one instance per conversation.
As Gavin said, in nested conversations any component in an outer conversation can be seen.