Question

I am working with a SOAP service that has a variable defined with leading underscores (one would assume private, but the documentation has specific examples where one must use them). In the WSDL it looks like this:

<xsd:element maxOccurs="1" minOccurs="0" name="__encoded_query" type="xsd:string"/>

Through some experimentation I have determined that, using named parameters in my client.service calls I am able to assign variables as normal, except for ones which have the leading underscore.

For example:

client.service.getRecords( name='server1' )

Produces the correct XML:

<ns1:getRecords>
  <name>server1</name>
</ns1:getRecords>

but if I attempt to use the parameter with the underscore:

client.service.getRecords( __encoded_query='name=server1' )

the XML which is produced does not include the parameter at all:

<ns1:getRecords/>

I am not sure whether this is a syntax nuance that I am unfamiliar with (either Python or suds) or perhaps suds attempting to be “smart” by protecting the variables based on the private variable convention. In any case, this is the documented way to use this web service so I need to figure out how to get suds to produce the XML including the __encoded_query block.

Answer 1

It’s not your fault, it’s a documented suds issue.