tmulders
17 years agoOccasional Contributor
Backwards compatibility
Hello,
We are at this time struggeling with the backwards compatibility of the created webservices and we are working out some possible solutions.
Situation: We are working with WSDL 1.0 and the new WSDL is 1.1 with three elements added to WSDL 1.1...We are supposed to work with the old WSDL for three months regardless of any changes.
In other words, the old requests should be accepted without the new elements. What will happen is that we will sent an old request without the three new elements, but we will receive a response WITH the three new elements. The response will not be according to our "old" WSDL, will SOAP UI accept that?...And is there a way that I can check that, I need to receive a failed assertion because of the new unknown elements. I have tried the assertion Schema compliance but the response I get is: Validation of SOAP encoded messages not supported.
Hope u can help us out. Thanks in advance.
Kind regards,
We are at this time struggeling with the backwards compatibility of the created webservices and we are working out some possible solutions.
Situation: We are working with WSDL 1.0 and the new WSDL is 1.1 with three elements added to WSDL 1.1...We are supposed to work with the old WSDL for three months regardless of any changes.
In other words, the old requests should be accepted without the new elements. What will happen is that we will sent an old request without the three new elements, but we will receive a response WITH the three new elements. The response will not be according to our "old" WSDL, will SOAP UI accept that?...And is there a way that I can check that, I need to receive a failed assertion because of the new unknown elements. I have tried the assertion Schema compliance but the response I get is: Validation of SOAP encoded messages not supported.
Hope u can help us out. Thanks in advance.
Kind regards,