Reputation: 4728
I have an issue with a webservice provided by a partner (I can't modify this service).
I must consume a WS-* web service (wsHttpBinding) with a .NET 2.0 client. I have the following exception:
SOAP header Action was not understood.
I know that it's not possible to communicate with WS- with .NET 2.0. I see it's possible to use WSE to communicate with WS-.
I do that but I have always the same error :
SOAP header Action was not understood
.
Is it possible to work around this problem to communicate with this service ?
Upvotes: 2
Views: 2376
Reputation: 3959
You might want to use the basicHttpBinding to get it working with a .NET 2.0 client. That binding already provides the compatibility required by older clients or other platforms. If you still decide to go with wsHttpBinding, you will have to use Microsoft WSE to create messages in the .NET 2.0 client that are compatible with the wsHttpBinding.
Upvotes: 2
Reputation: 1538
Usually consuming WCF services with .NET 2.0 applications changes the interface, adding a Boolean out parameter (success indicator), changing the return type to an out parameter and return type to void for each method.
Upvotes: -1