WSDL Validates...But I Don't Want it To
We ran into an issue this week when a new version of a web service was created. The version had been changed in the namespace but the soapAction still contained the prior version.
xmlns="http://www.mycompany.com/services/common/OurService/2.01"
<soap:operation soapAction="OurService/v2.0/OurServiceRead"/>
<soap:operation soapAction="OurService/v2.0/OurServiceUpdate"/>
Unfortunately, there's nothing wrong that prevents WS-I compliance from failing but it doesn't work when we try to actually call the service.
Visually I can look at the SOAPHttpsBinding but that relies on my actually remembering to check. Is there a way I can validate that the versions of my operations match that defined in my namespace?
OurServiceRead Literal false OurService/v2.0/OurServiceRead
OurServiceUpdate Literal false OurService/v2.0/OurServiceUpdate
xmlns="http://www.mycompany.com/services/common/OurService/2.01"
<soap:operation soapAction="OurService/v2.0/OurServiceRead"/>
<soap:operation soapAction="OurService/v2.0/OurServiceUpdate"/>
Unfortunately, there's nothing wrong that prevents WS-I compliance from failing but it doesn't work when we try to actually call the service.
Visually I can look at the SOAPHttpsBinding but that relies on my actually remembering to check. Is there a way I can validate that the versions of my operations match that defined in my namespace?
OurServiceRead Literal false OurService/v2.0/OurServiceRead
OurServiceUpdate Literal false OurService/v2.0/OurServiceUpdate