none
BizTalk Message Context to WCF Message Properties transferring RRS feed

  • Question

  • Hi everybody,

    We have a WCF message interceptors on two-way receive location with WCF-CustomIsolated adapter and two-way send port with WCF-Custom adapter.

    BeforeSendRequest method of IClientMessageInspector allows us to inspect WCF message properties before request message sending. WCF Message properties contains all properties from BizTalk Message Context in following format: namespace#name.

    BeforeSendReply method of IDispatchMessageInspector allows us to inspect WCF message properties before response message sending. WCF Message properties doesn't contain properties from BizTalk Message Context.

    Can you suggest, if it's possible at all, an approach to transfer BizTalk Message Context to the WCF Message Properties for the response?

    Thank you,
    Artem 

     


    Thursday, October 6, 2011 4:04 PM

Answers

  • heh, it was partially my fault. BizTalk WCF-Custom/WCF-CusomIsolated adapter transfers BizTalk Message Context to the WCF Message Properties in the response, but if your response doesn't contain a body (and for REST communication it's typical, for example, POST operations without any response) adapter will fail inside during message transformation. 

    As a workaround you can use Template with value "<bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="xml"/>" to construct an Output WCF Message body. 

    Monday, October 10, 2011 1:10 PM

All replies

  • Ok, 

    Maybe somebody has an idea how to transfer custom information from send to receive part not in a SOAP headers?
    It's necessary for REST services. An idea to transfer an HTTP headers, HTTP Status and so on...  This information resides in a WCF Message Properties but WCF-Custom/WCF-CustomIsolated adapter doesn't care about these properties.

    Monday, October 10, 2011 8:00 AM
  • heh, it was partially my fault. BizTalk WCF-Custom/WCF-CusomIsolated adapter transfers BizTalk Message Context to the WCF Message Properties in the response, but if your response doesn't contain a body (and for REST communication it's typical, for example, POST operations without any response) adapter will fail inside during message transformation. 

    As a workaround you can use Template with value "<bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="xml"/>" to construct an Output WCF Message body. 

    Monday, October 10, 2011 1:10 PM