I always thought that SOAP send and receive ports had to use the PassThruxxx pipelines, but I've found out today that not only is that not the case, the fact that I wasn't using an XmlReceive pipeline has been the cause of all my problems over the last couple of days.
If you use a PassThru promoted properties are not promoted (fairly obvious when you think about it), so receive shapes that have a correlation set attached are never activated, and messages go through with the "no matching subscription" error.
Aaargh.
No comments:
Post a Comment