|
| Hi All,
We have an orchestration in which we are getting updates to a message(M1) in
two branches (Branch1 and Branch 2) and requests for the message in third
branch (Branch3) of a listen shape.
The sequence of things is as follows:
Branch 1 gets the update to M1, assigns the updates through a message
assignment shape, assigns M1 back to a temporary variable of the same type
M1Temp.
Branch 2 gets a request for M1, this branch holds the update which was done
to M1 in Branch1. Sends the message M1 to the requestor.Life is good so far.
M1 and M1Temp are the same at this point (having the updates which came in
Branch1).
Branch 3 gets another update to the message, we use message assignment shape
to assign M1 == M1Temp, then move on to do some changes to M1 (updates which
just came in). The changes/updates are stored(changes/updates which came in
Branch3) in M1 but the updates which came in Branch1 seemed to be lost.
I cannot see why this would happen. Did some research and found this
following article
http://support.microsoft.com/?kbid=908169
Is there something going on like this article describes? If so how can we
invalidate the UnderlyingPart MessageBox representation in messsage
assignment shape?
or is there something we are missing here...
Any help/suggestions would really be appreciated.
Thanks in Advance,
KriS.
|
|