Contributions
Re: Validation of SOAP-Encoded messages is not supported
Thanks for your help. It does appear that the response being encoded is causing the problem, and unfortunately I have no control over that. It would be nice to be able to remove the encoding attribute from the response message and have SOAPUI validate the modified message instead of actually calling the endpoint, but I don't know of way to do that - maybe by setting up a mock response?4.2KViews0likes0CommentsRe: Validation of SOAP-Encoded messages is not supported
I generated the project + test cases from the WSDL file. I added a Schema Compliance assertion to the test case in question, specifying the WSDL file used to create the project when prompted. I received the error. (see screenshot attached)4.3KViews0likes2CommentsRe: Validation of SOAP-Encoded messages is not supported
Thanks for asking, Rich! I'm trying to do what is outlined here, and receiving the error which is the subject of my original post: Given a soap response message and a WSDL file, I just want to validate that the response message complies with the WSDL. Zip file containing response message and WSDL attached.4.3KViews0likes7Comments