0 Replies Latest reply on Aug 17, 2012 1:53 PM by John Doe

    Having separate instances of @ConversationScoped beans for each long-running conversation

    John Doe Newbie

      Hi. In my web-application I might have multiple simultaneous conversations(e.g. user accessing a wizard on page P in tab A and simultaneously the same page of the wizard  in tab B).

      The conversations are long-running. The problem is that although I mark my beans as @ConversationScoped, they still share the same field data. I.e. if I change the

      value of a field in the instance A of the conversation bean class, then it affects the value of the field in instance B of the bean class. How can separate the bean instances?


      PS. Using seam3 + jboss7.