Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Async messaging with WS-Addressing and the WCF-WSHttp adapter
- This topic has 3 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
July 7, 2008 at 11:18 AM #20082
Hi,
How can I set the MessageID SOAP header on an outbound message??? There is no WCF context property for MessageID. When I try to set the Message ID header using the WCF.OutboundCustomHeaders property, BizTalk overwrites it. I even checked to see if BizTalk was setting the MessageID header with the BTS.MessageID property, but alas, it is not. I just need to somehow get this message id so I can use it for correlation. Here is my scenario:
A dynamic routing orchestration sets the MessageID SOAP header of the outbound message, sends the message using the WCF-WSHttp adapter, initializes a correlation set with that MessageID, and waits for an async response. When BizTalk receives the response, a custom pipeline promotes the RelatesTo SOAP header from the inbound message. The RelatesTo header will match the MessageID header from the outbound message so BizTalk can correlate this response message with the original request message.
Please help!
-
July 9, 2008 at 7:04 AM #20097
I tried one more thing: creating a custom property schema for the MessageID and promoting it before sending it. Here’s what I did:
-
Created a new property schema with namespace: http://www.w3.org/2005/08/addressing (WS-Addressing namespace)
-
Added a property: MessageID
-
Created a new correlation type and set for the MessageID property.
-
Set the MessageID on my outbound message before sending it.
-
Had the send shape initialize the correlation set.
-
Confirmed that the MessageID property was in fact set and promoted before hitting the send port.
-
The WCF adapter ignored my property and generated it’s own MessageID on the outbound SOAP envelope.
Any more ideas?
This shouldn’t be this hard! WS-Addressing is one of the core standards that the WCF-WSHttp adapter is supposed to address!
-
July 9, 2008 at 12:41 PM #20102
Random idea, how about constructing the ws-addressing header in the orchestration and inserting into WCF.OutboundCustomHeaders
-
July 9, 2008 at 5:28 PM #20104
Tried that… didn’t work… The WCF-WSHttp adapter overwrites my message id in the OutboundCustomHeaders with its own newly generated message id. I also thought maybe the WCF-Cusom adapter wouldn’t care so much about all the WS-Adressing headers and wouldn’t overwrite my OutboundCustomHeaders. Nope, that adapter overwrites them too. Oh, the heartache!
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.