Error handling XSD with nested scheme #658
Description
We replaced SUDS with Zeep and are very happy with the results, kudo's for this excellent lib!
The SOAP server facilitates some complexer call's to search in data: these call's seem to violate some rules in Soap (or in Zeep) so depending on the endpoint (table); we get results or not. I needed to disable strict mode to get results at all.
The problem seems related to the return types that are links to the original content. I also included an response that shows how a normal response with multiple items is facilitated. Zeep fails on some of the responses for the find. I noticed 2 cases:
a) Data isn't available in an soap object attribute att all but in an attribute: _raw_elements. (wrong_request.xml and wrong_response.xml)
b) Data is available in the normal way. (correct_request.xml and correct_response.xml)
For both cases the SUDS based solution returns SOAP objects that mimic the behaviour of a call to GetProductById or GetAllProducts: e.g. it would return Products instead of links to Products.
Mandatory information:
- The version of: tested with zeep 2.4.0 & 2.5.0
- The WSDL you are using: see https://github.com/acidjunk/zeep_example/tree/master/wsdl
- An example script: see https://github.com/acidjunk/zeep_example/blob/master/an_example_script.py