Correlations again

["Eckenfels. Bernd" <B.Eckenfels@seeburger.de>]

Hello,

I feel a bit uneasy understanding the corelation example in the spec on page 94.

There is a initial receive into variable shipRequest which will initiate a "shipOrder" correlation set, which uses "shipOrderID" property, which is used inside shippingRequestMsg as /ShippingOrderRequestHeader/shipOrderID and inside "shippingNoticeMsg" as "/ShipNoticeHeader/shipOrerID"

in the following activites (in case of ship complete) the content of itemsCount is copied from shipRequest to shipNotice, then shipNotice is send to the customer, using a correlation (initiate=no) on shipOrder.

What purpose does this correlation have in a exectuable process?

a) it will use the values of the properties for that property set and change the value of the elements send to the partner with the values required to corrrelate (i.e. in the shippingNotice message /ShipNoticeHeader/shipOrderId will be set to the value of the initial mesage.

b) like a, but it wil lalso change the variable (i.e. it will set /ShipNoticeHeader/shipOrderId in shipNotice variable to the value

c) it will not set any values, it will just verify, that the variable was filled correctly



a+b make sence, since otherwise the sample code will never work (shipOrderID would be uninitialized)
c is my favorite interpretation, am i right? if so, do we need to fix samples?

the sample on p52 is even more complicated for me, since there is no property which has aliases in more than one message.

Ah, and yes, if c) is right, then the question of Issue 37 applies, what will happen if the content of the variable which is about to be send does not match the expected values (as defined in the properties of the correlation set)

Greetings
Bernd