Thursday 15 March 2012

.net - MsmqMessage<T> necessary? -


I am analyzing a BizTalk application (aka orchestra) that communicates with the WCF service via MSMQ. I was thinking that one of the WCF service implementations has an MSMMA message as a parameter in the service method. I was expecting contract type T instead of an MSMMAE.

This is not really an unidentified bond, because there is a specific MSMUP type in the WCF service system.

Is it really necessary to have an MsmqMessage binding type when communicating with a WCF MSMQ service from a BizTalk app?

This is the current code:

  Public Zero SaveDocumentASync (MsmqMessage & lt; MyDocument & gt; msg) {}  

It should:

  Public Zero SaveDocumentASync (MyDocument msg) {}  

As far as I remember, the reason for this is that you are using an MSM inactivebandbanding and not netmassbbiding. MsmqMessage & LT; T & gt; Provides access to MSMQ message properties (both on sending and receiving) which can be useful on many scenarios.


No comments:

Post a Comment