Gino – Orch-A needs to basically call Orch-B, but instead of using the CALL shape at this client, they send a message using direct binding and they do correlation.
We opened a Microsoft indicident on this. It turns out that it is a problem with the SOAP Headers. We have a pipeline that promotes the SOAP headers when the file is dropped in a flat file or MSMQ, but there is now way to promote the fields with direct binding – i.e. no pipeline can be assigned to direct binding.
Thus, when Orch-B initializes correlation on the return message, that in effect promotes the field from the SOAP header. This is not a problem when using \”normal\” promoted fields in the message itself.
Interestingly enough, a property can be in the \”context\” message, and still have the isPromoted value set to either true or false. I’m not sure why all context fields are not considered promoted, but they are not – Microsoft said \”by design\” and for efficiency.
Neal Walters
http://Biztalk-Training.com