- This topic has 3 replies, 1 voice, and was last updated 7 years, 8 months ago by
.
-
Posts
-
-
Hi all,
I have a WCF service that has exposed some 1 way services (I.e. the IsOneWay attribute set to true).
I added these into BizTalk (via add generated items) and can call them correctly. The problem is, they always suspend.
BizTalk waits for a respones and doesn’t get anything (other than a
HTTP 202) and therefore suspends the orchestration and attempts to
retry sending to the service (which actually works).Is there a way to get correct 1 way behaviour to work with BizTalk? I.e
fire and forget? I do not want to recreate a specal “BizTalk” version
of my service with fake 1 way operations.Any help would be greatly appreciated.
Kind regards,
TM -
Is your send port one-way or two-way? You need to use a one-way send port to call a one-way service.
-
Hi rusel, thanks for the reply.
Yes the sendport was 1-way, however this was not the issue. It turns out, BizTalk 2006 R2 does not support 1 way web services. A massive error in ways, but what to do.
TM
-
Yeah, I saw your post on TechNet where someone answered that 1-way services aren’t supported. That’s unfortunate, but the good thing here is that the WCF stack gives you the flexibility to make it work. The custom binding option sounded pretty promising, and that’s the way I would go if I were in your situation (unless I could just change the service to 2-way of course).
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.