SOAP 1.2 Python client ?

B

BlueBird

Hi,

I am looking for a SOAP 1.2 python client. To my surprise, it seems
that this does not exist. Does anybody know about this ?

The following clients seem to be both unmaintained and still
supporting only SOAP 1.1 :

- SUDS
- zsi
- SOAPy


cheers,

Philippe
 
W

Waldemar Osuch

Hi,

I am looking for a SOAP 1.2 python client. To my surprise, it seems
that this does not exist. Does anybody know about this ?

The following clients seem to be both unmaintained and still
supporting only SOAP 1.1 :

- SUDS
suds unmaintained? I beg to differ.
 
B

BlueBird

BlueBird, 03.03.2010 17:32:


SOAP may be an overly bloated protocol, but it's certainly not black magic.
It's not hard to do manually if you really need to:

http://effbot.org/zone/element-soap.htm

But this requires a goog knowloedge of SOAP, in order to parse
everything correctly. The reason I want to use a ready-made client is
that I have about zero knowledge about SOAP, and even more in the
differences between SOAP 1.1 and 1.2 .

cheers,

Philippe
 
L

lbolla

But this requires a goog knowloedge of SOAP, in order to parse
everything correctly. The reason I want to use a ready-made client is
that I have about zero knowledge about SOAP, and even more in the
differences between SOAP 1.1 and 1.2 .

cheers,

Philippe


I use a thin custom-made python wrapper around gSoap[1], which is tens
of times faster than ZSI.
L.


[1] http://www.cs.fsu.edu/~engelen/soapdoc2.html
 
B

BlueBird

But this requires a goog knowloedge ofSOAP, in order to parse
everything correctly. The reason I want to use a ready-made client is
that I have about zero knowledge aboutSOAP, and even more in the
differences betweenSOAP1.1 and 1.2 .

Philippe

I use a thin custom-made python wrapper around gSoap[1], which is tens
of times faster than ZSI.

I looked at gSoap and the solution seemed really nice. They can
generate C that I can call with ctypes.

The only problem is that I am working on a closed source software and
their licensing cost for close source were too expensive for my
company.

After much much digging, we found out the problem and managed to solve
it with SUDS. When calling a .NET service, you should not reference
the soap envelope spec with 'http://schemas.xmlsoap.org/soap/
envelope/' but with 'http://schemas.xmlsoap.org/soap/envelope' .
The .NET server implementation seems to be very picky about the
last / .

Yeah for SUDS and oooooh for .NET

cheers,

Philippe
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,996
Messages
2,570,238
Members
46,826
Latest member
robinsontor

Latest Threads

Top