2 Replies Latest reply on Sep 17, 2006 6:02 PM by pmuir

    Stateful Session Bean Instances and Conversations

    jgilbert
    jgilbert Sep 14, 2006 7:57 PM

      I have a SFSB involved in a conversation that manages an instance of an entity bean. and the user can have multiple conversations. when i switch between conversations the state seems to be the state of the last used conversation. Is an instance of the SFSB created for each conversation? I would think the answer is no. If no, does it make sense to use a SFSB? Or should I just use bijection to store the entity bean in the conversation?

      • 2285 Views
      • Tags:
        • 1. Re: Stateful Session Bean Instances and Conversations
          bfo81
          bfo81 Sep 15, 2006 12:30 PM (in response to jgilbert)

           

          @Stateful
@Scope(ScopeType.CONVERSATION) //I think this is the default scope so you might leave it out
@Name("...")
public class WhateverBean implements Whatever, Serializable {

 @In(required=false) //should be initially created in here
 @Out
 private AnEntity entity;

...
}


          If you do it like this, there should be a separate SFSB for every conversation and every instance has its very own entity instance.

            • Actions
          • 2. Re: Stateful Session Bean Instances and Conversations
            pmuir
            pmuir Sep 17, 2006 6:02 PM (in response to jgilbert)

            It depends on you conversation propogation. You can control this using the s:link tag or the conversationPropogation request parameter. Unless you @End a conversation or set the conversationPropogation to none you remain in the current conversation.

              • Actions