Hi Van Nguyen.
This seems to be a major problem for a few service implementations
when
it sends elements when there's no data. Would it be possible to patch
this upstream?
https://github.com/ExactTarget/FuelSDK-Python/tree/master/Suds%20Changes
I just looked through some old news-postings I had flagged and ran
into this one. A bit late, I know, but I was wondering if this is
something you are still involved in and have information on or if it is
just 'old junk' that should better be left forgotten?
I looked through the patch, and, as a general purpose patch, it does
some bad things. ;-) I believe there was a problem you were trying to
solve with it, but I could not find the exact problem description anywhere.
From looking at the WSDL mentioned in your patch project, my first
guess is that your WSDL contained <choice> XSD data structures which the
original suds implementation does not handle correctly. If that is so,
than I'd be interested to know if using the suds-jurko fork resolves
your issues. You can find it on either:
- BitBucket -
http://bitbucket.org/jurko/suds
- PyPI -
http://pypi.python.org/pypi/suds-jurko
If something else is the issue, I'd need a more detailed use case to
look into it, e.g.:
- exact call
- exact WSDL
- exact constructed SOAP request
- exact expected SOAP request.
Best regards,
Jurko Gospodnetić