suds

I would like to send my hand build xml by SUDS using WSDL. I found, that I can do it like that: xml = Raw(""" <SOAP-ENV:Envelope xmlns:ns0="urn:ca:std:cdc:tech:xsd:cdc.001.01" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <ns1:Body> <ns0:GetAccountBalance> <ns0:Document> <myData> something </myData> </ns0:Document> </ns0:GetAccountBalance> </ns1:Body> </SOAP-ENV:Envelope> """) print client.service.GetAccountBalance(xml) But using this method SUDS sends:

I'm using python suds library to make a SOAP client based on a local wsdl file. My goal is to use Twisted as the backend so I query the SOAP servers in a asyncronous way. I know this topic has been covered different times ( here1 , here2 ), but I still have some questions. I've seen three different approaches to use twisted with suds: a) Applying this patch to the suds library. b) Use twisted-suds , which is a fork of suds. c) Influenced by this post , I implemented Client_Async suds client using the twisted deferToThread operation, (fully working gist can be found here . I also implemented a

This question is similar to this one: How can I output what suds is generating/receiving? The problem is that I am using the suds fork by Jurko and after version "0.4.1 jurko 5" the Client.last_sent() , Client.last_received() methods have been removed. So the question is how can we replace their functionality on new suds versions? PS. I know that I can decrease the debugging level but I would like if possible to be able to inspect the input/output programmatically. You can use the MessagePlugin to do this from suds.plugin import MessagePlugin class LogPlugin(MessagePlugin): def sending(self,

Environment: Python v2.6.2 suds v0.3.7 The WSDL (server) I work with, have the following schema sub-sections (I tried to write it clearly using plain text) - [ sub-section #1 ] searchRequest: (searchRequest){ userIdentification = (userIdentification){ username = "" password = "" } itineraryArr = (itineraryArray){ _arrayType = "" _offset = "" _id = "" _href = "" _arrayType = "" } ... ... [ sub-section #2 ] itinerary: (itinerary){ departurePoint = (locationPoint){ locationId = None radius = None } arrivalPoint = (locationPoint){ locationId = None radius = None } ... ... There is no problem with

I am currently looking into implementing a client which will use an existing extensive SOAP management API. I looked into different SOAP implementations like pysimplesoap and SUDS . While the first had problems parsing the WSDL because of too much recursions, suds worked fine (but slow) and I really like module. However, there seem to be several issues with SUDS like the high memory consumption, the WSDL parsing speed and missing support for some WSDL attributes (eg. choice attribute). While there are a lot of people actively committing bug reports and patches, there was no release of SUDS

I need to interact with a SOAP service and am having a lot of trouble doing so; would really appreciate any pointers on this. The original error message was: org.apache.axis2.databinding.ADBException: Any type element type has not been given After some research, it turns out that this is a disagreement between SUDS and the server has to how deal with type="xsd:anyType" on the element in question. I've confirmed using SOAPUI and after advice that the problem can be fixed by taking these steps: Adding xsi:type="xsd:string" to each element which causes problems Adding xmlns:xsd="http://www.w3.org