Problem with WSDL and namespace

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a client with this WSDL: client = 
SoapClient(wsdl="https://api.dc2.computing.cloud.it/WsEndUser/v2.4/WsEndUser.svc
?wsdl",trace=True)
2. Try using the following function (haven't tried other ones yet): 
result=client.SetEnqueueServerStop(serverId=37)

What is the expected output? What do you see instead?

I should get an xml answer from the server, like {'SetEnqueueServerStopResult': 
{'ResultCode': 15, 'Success': False, 'ResultMessage': u'Could not find a server 
with Id 37\r\nExceptionCode=15\r\n', 'ExceptionInfo': None}} . Instead I get 
the following error:

 File "C:\Python27\lib\site-packages\pysimplesoap\client.py", line 188, in call
    raise SoapFault(unicode(response.faultcode), unicode(response.faultstring))
pysimplesoap.client.SoapFault: a:InternalServiceFault: Error in deserializing 
body of request message for operation 'SetEnqueueServerStop'. 
OperationFormatter encountered an invalid Message body. Expected to find node 
type 'Element' with name 'SetEnqueueServerStop' and namespace 
'https://api.computing.cloud.it/WsEndUser'. Found node type 'Element' with name 
'SetEnqueueServerStop' and namespace 
'https://api.computing.cloud.it/WsEndUser/Imports'

What version of the product are you using? On what operating system?

Python 2.7.5 on windows 7, pysimplesoap installed using PIP (1.05a)

Please provide any additional information below.

Works if before making the actual call I manually
client.namespace="https://api.computing.cloud.it/WsEndUser"

Original issue reported on code.google.com by marco.sa...@gmail.com on 20 Jun 2013 at 12:53

[GoogleCodeExporter]

This should be fixed in trunk (version 1.11, revision a16a09aa50ea):

https://code.google.com/p/pysimplesoap/source/detail?r=a16a09aa50ea01544ed7e5439
dfb63bed65bf8a8

(test added)

Original comment by reingart@gmail.com on 29 Aug 2013 at 8:32

• Changed state: Started

[GoogleCodeExporter]

it seems fixed and tests are passing, so this issue is closed due inactivity, 
if the problem persist, please fill a new issue

Original comment by reingart@gmail.com on 13 Sep 2013 at 3:36

• Changed state: Fixed