We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Forum Discussion
Solved
Validation of SOAP-Encoded messages is not supported
I'm trying to use SOAPUI to determine if the response I'm getting back from a SOAP API is consistent with its own WSDL schema. Why is SOAPUI not able to do this? Attached are the response and the...
- Hey pmartin73,
Ah...i understand. So the assertion is having an issue, right?
Ok. I did abit of googling. It seems this can occur if the content of the .wsdl is erroneous. I dont mean malformed or invalid, i mean erroneous relative to certain attribute values used.
There is an "encoding" attribute that if set illegally (illegally relative to the SOAP message layer protocol) then this will cause the assertion to fail with the response you are seeing.
Theres a stackoverflow link that may help -->>https://stackoverflow.com/questions/24411468/error-validation-of-soap-encoded-messages-not-supported/44848162
Theres alao another link with a lot more low level info that could help -->> https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc19050_.htm
In summary. Theres a problem with the wsdl and until you fix the issue youll keep getting this if you try using the schema assertion or even probably any SOAP related assertion as the wsdl content breaks the SOAP rules in some way.
Hope this helps!
Ta
Rich
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)
Hey pmartin73,
Ah...i understand. So the assertion is having an issue, right?
Ok. I did abit of googling. It seems this can occur if the content of the .wsdl is erroneous. I dont mean malformed or invalid, i mean erroneous relative to certain attribute values used.
There is an "encoding" attribute that if set illegally (illegally relative to the SOAP message layer protocol) then this will cause the assertion to fail with the response you are seeing.
Theres a stackoverflow link that may help -->>https://stackoverflow.com/questions/24411468/error-validation-of-soap-encoded-messages-not-supported/44848162
Theres alao another link with a lot more low level info that could help -->> https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc19050_.htm
In summary. Theres a problem with the wsdl and until you fix the issue youll keep getting this if you try using the schema assertion or even probably any SOAP related assertion as the wsdl content breaks the SOAP rules in some way.
Hope this helps!
Ta
Rich
Ah...i understand. So the assertion is having an issue, right?
Ok. I did abit of googling. It seems this can occur if the content of the .wsdl is erroneous. I dont mean malformed or invalid, i mean erroneous relative to certain attribute values used.
There is an "encoding" attribute that if set illegally (illegally relative to the SOAP message layer protocol) then this will cause the assertion to fail with the response you are seeing.
Theres a stackoverflow link that may help -->>https://stackoverflow.com/questions/24411468/error-validation-of-soap-encoded-messages-not-supported/44848162
Theres alao another link with a lot more low level info that could help -->> https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc19050_.htm
In summary. Theres a problem with the wsdl and until you fix the issue youll keep getting this if you try using the schema assertion or even probably any SOAP related assertion as the wsdl content breaks the SOAP rules in some way.
Hope this helps!
Ta
Rich
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?