2 Replies Latest reply on Jul 28, 2009 12:37 PM by magiccreative

    Component outjected in CONVERSATION scope phenomenon

    magiccreative

      hi,


      there is an interesting situation with an object outjected in CONVERSATION scope. 2 conversations are opened parallely and a third page with debug is viewed to check the ids of the objects. What happens is very strange.


      If the pages are opened one after the other, with enough time to load between openning the end result is an object with the same id in both conversations. Now what is amazing is that if one clicks fastly and opens all 3 pages in different tabs again, but they load together, the ids of the outjected object are different.


      Does anyone have any explanation of this phenomenon? How can at all an object outjected in conversation scope be the same for two different conversations (the components that initialise it are also in different conversations, not in shared session for example)

        • 1. Re: Component outjected in CONVERSATION scope phenomenon
          kukeltje.ronald.jbpm.org

          But are they the same? If you use one, is te other also updated?

          • 2. Re: Component outjected in CONVERSATION scope phenomenon
            magiccreative

            it is important to note that this happens only when both conversations are nested and have the same parent. When the type is change to propagation none, then it works as expected.


            So for the nested situation what happens is: There is an object annotated with Out. One opens C1 and this object is set, lets say Obj1. In C2 it is Obj2. In C1 now we still have Obj1 in debugger. But when the transaction comes to an end, in database are written the values from Obj2.


            Do you have any idea why the Object is with the same objectid in debug page, for example - b2ata001, when opened slowly and when C1 and C2 opened in parallel the ids are something like b2ata001 and sa3o2ll (for example).