I have the following bridge script for WCF: a WCF client using the basicHttp binding talking to the routing service that redirects the request to the service using netTcp.
Client ↔ basicHttpBinding (SOAP 1.1)↔ Router Service ↔ netTcpBinding (SOAP 1.2)↔ Service
The routing functionality works fine until we provide a service to our C ++ client who uses the gSOAP library to send messages to the service. If the C ++ client directly communicates with the Service, the call is successful; however, as soon as he tries to contact through the routing service, he fails.
The service receives a redirected message, but throws an exception as soon as it tries to deserialize the message. The error message that is returned from the service is this System.ServiceModel.Dispatcher.NetDispatcherFaultExceptionsaying"The formatter threw an exception while trying to deserialize the message…"
The problem seems to be caused by the protocol bridge. If I do not use protocol bridges, i.e. I use basicHttp throughout the entire call chain, the C ++ client (and message routing) works as expected.
I cannot figure out how to solve this problem. I understand that the routing service is for the WCF-WCF broker, but the problem seems to be isolated only from calls coming from the C ++ gSOAP client. I tried using some web service testing tools (soapUI, soapSonar) to see if I can reproduce the problem, but they seem to work fine. Any help or guidance would be appreciated.
,