Forum Discussion
remikeo
13 years agoNew Contributor
Actually these services are pretty similar to webservices except they don't use SOAP or any WS standard.
The request is a HTTP-POST which content is an XML message and the response is also an XML message.
Both messages are described in an XSD schema but there's no WSLD and since the messages are not compliant with SOAP there couldn't be any way to describe them in a WSDL.
Unfortunately these are legacy services that we cannot change.
I can use SoapUI to test them (even if I have to write the request myself instead of having SoapUI generating one with '?' values) and I can specify some assertions to validate the response content.
Now I would like to use SoapUI to create a dynamic Mock implementation for these services as I already do with the SOAP ones.
The request is a HTTP-POST which content is an XML message and the response is also an XML message.
Both messages are described in an XSD schema but there's no WSLD and since the messages are not compliant with SOAP there couldn't be any way to describe them in a WSDL.
Unfortunately these are legacy services that we cannot change.
I can use SoapUI to test them (even if I have to write the request myself instead of having SoapUI generating one with '?' values) and I can specify some assertions to validate the response content.
Now I would like to use SoapUI to create a dynamic Mock implementation for these services as I already do with the SOAP ones.