Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In WSDL1.1, does each binding/operation/soap:operation/@soapAction have to be unique inside it’s containing binding? If not, how does the SOAP/WSDL server know which “matching” operation to invoke?
I’m pretty sure the SOAP Action has to be unique, it’s the part of the request (for HTTP transports, it’s in the form of an HTTP header) which uniquely identifies the operation. Essentially, the SOAP Action is the URI of the operation.
Having said that, in many cases the SOAP action header is redundant, since the type of the SOAP payload is often enough to uniquely identify the target operation.