Hi there,
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
Cheers,
Van Nguyen Developer [image: JBA] http://www.jbadigital.com/ JBA Online Consultancy W: www.jbadigital.com A: Level 1, 2 Darling Street, South Yarra, Melbourne 3141 The information contained in this email is confidential and is intended for the use of the individual or entity named above. If the receiver of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this email is strictly prohibited. If you have received this e-mail in error, please notify our office by telephone. JB/A and their employees do not represent that this transmission is free from viruses or other defects and you should see it as your responsibility to check for viruses and defects. JB/A disclaims any liability to any person for loss or damage resulting (directly or indirectly) from the receipt of electronic mail (including enclosures).
Greetings Van,
Thanks for sharing your patch with the community. Unfortunately, the official maintainer of Suds has not been actively involved with the project for some time, so I wouldn't hold your breath on getting the patch committed to the main Suds upstream.
That said, there are a few folks on the list working on Suds forks. I can't speak for them, but I suspect they would be your best to get the patch included in a Suds codebase.
Regards,
- Chris
On Tue, Jul 23, 2013 at 7:25 PM, Van Nguyen van@jbadigital.com wrote:
Hi there,
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
Cheers,
Van Nguyen Developer [image: JBA] http://www.jbadigital.com/ JBA Online Consultancy W: www.jbadigital.com A: Level 1, 2 Darling Street, South Yarra, Melbourne 3141 The information contained in this email is confidential and is intended for the use of the individual or entity named above. If the receiver of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this email is strictly prohibited. If you have received this e-mail in error, please notify our office by telephone. JB/A and their employees do not represent that this transmission is free from viruses or other defects and you should see it as your responsibility to check for viruses and defects. JB/A disclaims any liability to any person for loss or damage resulting (directly or indirectly) from the receipt of electronic mail (including enclosures).
suds mailing list suds@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/suds
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ć
-
Chris Sears -
Jurko Gospodnetić -
Van Nguyen