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?
You are creating nested conversations. They will see the component from the outer conversation.
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
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?
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.
Thanks for the info. So where is the state saved for multiple conversations on the same instance?
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.