posted on Friday, August 04, 2006 9:19 PM
by
doval
SOAP Living
I have been working on some software that "really" needs to play well with others.
I used my usual tricks with services but there we still some platforms that did not like my SOAP. Getting down into the guts of the problem I found problems with the MS header "SOAPAction". After cleaning up my WSDL and adhering strickty to WSI I found that MS thought all my web methods had the same SOAPAction. After some research I found the magic attribute:
[SoapDocumentService(RoutingStyle = SoapServiceRoutingStyle.RequestElement)]
The MS error:
The methods getVendorVersion and poll use the same SOAPAction ''. When the RoutingStyle of the XML Web service is SoapAction, SOAPAction values must be unique across methods on the XML Web service. You can change the SOAPAction with the Action parameter to the SoapDocumentMethod or SoapRpcMethod attributes, or you can specify a RoutingStyle of RequestElement on the XML Web service.