From bradallen137 at gmail.com Mon Mar 1 11:34:10 2010 From: bradallen137 at gmail.com (Brad Allen) Date: Mon, 1 Mar 2010 04:34:10 -0600 Subject: [Soap-Python] The Python SOAP community: past, present, future Message-ID: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> Hello, This new Python-SOAP mailing list is an attempt to form a more cohesive community among the Python developers who work with SOAP; whether it succeeds depends on whether anyone else shares that interest. During the past week 49 people have signed up to join this list, so at least we have enough interest to fire up a a conversation :-). I'd like to start by asking whether anyone here can help piece together the story of the various Python SOAP frameworks: how did each of them come about, what niche is each serving today, which is still actively maintained, and does anyone have in mind specific future directions for these frameworks? Please feel free to chime in with your experiences and opinions. From burak.arslan at arskom.com.tr Mon Mar 1 12:50:18 2010 From: burak.arslan at arskom.com.tr (Burak Arslan) Date: Mon, 01 Mar 2010 13:50:18 +0200 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> References: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> Message-ID: <4B8BA9FA.1080004@arskom.com.tr> Hello there, First, I'd like to thank Brad for his efforts, i think the python soap community long needed this. Brad Allen wrote: > I'd like to start by asking whether anyone here can help piece > together the story of the various Python SOAP frameworks: how did each > of them come about, what niche is each serving today, which is still > actively maintained, and does anyone have in mind specific future > directions for these frameworks? > I'm using soaplib as a soap server and suds as a soap client. I'm inclined to say that both are mature projects, and I have them running in production (with a few small patches). I heard about zsi and soappy, and also that twisted has some form of soap support via soappy. Here are two proposed feature directions that, imho, the unified python soap (tups for short?) community should consider. 1) The code that performs the (de-)serialization between native python objects and soap xml documents, with the wsdl machinery that goes along with it, should be separated and organized under a new package. I'm imagining a SoapService object that can get its data (service definitions) from both suds-like parse-the-wsdl way, or the soaplib-like define-the-services-and-objects way. 2) the client/server logic should live outside this effort. awaiting your feedback, best regards, burak From estein at dyn.com Mon Mar 1 14:32:24 2010 From: estein at dyn.com (Eric Stein) Date: Mon, 1 Mar 2010 08:32:24 -0500 (EST) Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <3328574.56071267450245388.JavaMail.root@mail.corp> Message-ID: <22705760.56111267450344988.JavaMail.root@mail.corp> At least in ZSI, there is too much marriage (IMHO) between the parser/serializer and the built-in web server. Perhaps this means I should be using a different library, but the investment made already is too much to waste switching to soaplib or similar. One of the biggest deficiencies I've observed in the python SOAP library space is documentation. For example, the latest version of ZSI (2.1-alpha1) does not appear to have a user's guide out yet. On the subject of unifying the libraries into some common API: this doesn't seem productive to me. Eric ----- Original Message ----- From: "Burak Arslan" To: soap at python.org Sent: Monday, March 1, 2010 6:50:18 AM GMT -05:00 US/Canada Eastern Subject: Re: [Soap-Python] The Python SOAP community: past, present, future Hello there, First, I'd like to thank Brad for his efforts, i think the python soap community long needed this. Brad Allen wrote: > I'd like to start by asking whether anyone here can help piece > together the story of the various Python SOAP frameworks: how did each > of them come about, what niche is each serving today, which is still > actively maintained, and does anyone have in mind specific future > directions for these frameworks? > I'm using soaplib as a soap server and suds as a soap client. I'm inclined to say that both are mature projects, and I have them running in production (with a few small patches). I heard about zsi and soappy, and also that twisted has some form of soap support via soappy. Here are two proposed feature directions that, imho, the unified python soap (tups for short?) community should consider. 1) The code that performs the (de-)serialization between native python objects and soap xml documents, with the wsdl machinery that goes along with it, should be separated and organized under a new package. I'm imagining a SoapService object that can get its data (service definitions) from both suds-like parse-the-wsdl way, or the soaplib-like define-the-services-and-objects way. 2) the client/server logic should live outside this effort. awaiting your feedback, best regards, burak _______________________________________________ Soap mailing list Soap at python.org http://mail.python.org/mailman/listinfo/soap From estein at dyn.com Mon Mar 1 14:44:04 2010 From: estein at dyn.com (Eric Stein) Date: Mon, 1 Mar 2010 08:44:04 -0500 (EST) Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> Message-ID: <23523839.56171267451044795.JavaMail.root@mail.corp> A thing to keep in mind is that SOAPpy is a dead project, having not had a release since 2005. Eric ----- Original Message ----- From: "Brad Allen" To: soap at python.org Cc: sam at zeomega.com, "Jeff Rush" Sent: Monday, March 1, 2010 5:34:10 AM GMT -05:00 US/Canada Eastern Subject: [Soap-Python] The Python SOAP community: past, present, future Hello, This new Python-SOAP mailing list is an attempt to form a more cohesive community among the Python developers who work with SOAP; whether it succeeds depends on whether anyone else shares that interest. During the past week 49 people have signed up to join this list, so at least we have enough interest to fire up a a conversation :-). I'd like to start by asking whether anyone here can help piece together the story of the various Python SOAP frameworks: how did each of them come about, what niche is each serving today, which is still actively maintained, and does anyone have in mind specific future directions for these frameworks? Please feel free to chime in with your experiences and opinions. _______________________________________________ Soap mailing list Soap at python.org http://mail.python.org/mailman/listinfo/soap From cdevienne at gmail.com Mon Mar 1 15:46:18 2010 From: cdevienne at gmail.com (Christophe de VIENNE) Date: Mon, 1 Mar 2010 15:46:18 +0100 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <23523839.56171267451044795.JavaMail.root@mail.corp> References: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> <23523839.56171267451044795.JavaMail.root@mail.corp> Message-ID: <57b32ba81003010646k7165d35fo391a53b6b5b74954@mail.gmail.com> Hello, Nice to meet you all, Brad Allen write: > I'd like to start by asking whether anyone here can help piece > together the story of the various Python SOAP frameworks: how did each > of them come about, what niche is each serving today, which is still > actively maintained, and does anyone have in mind specific future > directions for these frameworks? > I will say a few words about TurboGears WebServices [1] which I maintain since may 2008 (the project was initialy released by Kegin Dangoor in 2006). It provides a very easy way to implement multi-protocol web services in TurboGears [2] applications. Among them, SOAP, which has a minimalistic server-side implementation. "minimalistic" meaning that the goal is no to support the whole SOAP protocol but to implement a subset of it, which will allow a natural use of the API created using tgws. We are currently improving the soap support (better native types support, default values, better error handling...). Best regards, Christophe de Vienne [1] http://code.google.com/p/tgws/ [2] http://www.turbogears.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From erevilla at yaco.es Mon Mar 1 16:00:03 2010 From: erevilla at yaco.es (Ernesto Revilla) Date: Mon, 01 Mar 2010 16:00:03 +0100 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <4B8BA9FA.1080004@arskom.com.tr> References: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> <4B8BA9FA.1080004@arskom.com.tr> Message-ID: <1267455603.10390.9.camel@trac.localdomain> Hi. I'm using the same: - soaplib as server: I love the WSDL generation. We use it from inside Django, like this [1] (see also other django snippets [2] ) - soaplib-django test client like this [3] - suds as "Consume WSDL" webservice client With soaplib, I stuck to the old version (0.7.x), as it works well enough for me. I still didn't test it with 0.8.x. The motivation I had for using a new version of soaplib was to use ws-addressing as ws-security authentication username token. But this is still not implemented, so I switched to suds. It would be great to have a unified, maintained SOAP package, especially for communicating with Apache Axis, .NET, etc. frameworks. A community process with a PEP at the final would be great. Regards. Erny [1] http://www.djangosnippets.org/snippets/979/ [2] http://www.djangosnippets.org/tags/soaplib/ [3] http://www.djangosnippets.org/snippets/1406/ El lun, 01-03-2010 a las 13:50 +0200, Burak Arslan escribi?: > Hello there, > > First, I'd like to thank Brad for his efforts, i think the python soap > community long needed this. > > Brad Allen wrote: > > I'd like to start by asking whether anyone here can help piece > > together the story of the various Python SOAP frameworks: how did each > > of them come about, what niche is each serving today, which is still > > actively maintained, and does anyone have in mind specific future > > directions for these frameworks? > > > > I'm using soaplib as a soap server and suds as a soap client. I'm > inclined to say that both are mature projects, and I have them running > in production (with a few small patches). > > I heard about zsi and soappy, and also that twisted has some form of > soap support via soappy. > > Here are two proposed feature directions that, imho, the unified python > soap (tups for short?) community should consider. > > 1) The code that performs the (de-)serialization between native python > objects and soap xml documents, with the wsdl machinery that goes along > with it, should be separated and organized under a new package. I'm > imagining a SoapService object that can get its data (service > definitions) from both suds-like parse-the-wsdl way, or the soaplib-like > define-the-services-and-objects way. > > 2) the client/server logic should live outside this effort. > > awaiting your feedback, > > best regards, > burak > > > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap From bradallen137 at gmail.com Mon Mar 1 16:45:30 2010 From: bradallen137 at gmail.com (Brad Allen) Date: Mon, 1 Mar 2010 09:45:30 -0600 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <57b32ba81003010646k7165d35fo391a53b6b5b74954@mail.gmail.com> References: <4957f1ef1003010234t9b8246ct975035ab09252252@mail.gmail.com> <23523839.56171267451044795.JavaMail.root@mail.corp> <57b32ba81003010646k7165d35fo391a53b6b5b74954@mail.gmail.com> Message-ID: <4957f1ef1003010745j5f84479g7129cf0ed93e6aec@mail.gmail.com> On Mon, Mar 1, 2010 at 8:46 AM, Christophe de VIENNE wrote: > I will say a few words about TurboGears WebServices [1] which I maintain > since may 2008 (the project was initialy released by Kegin Dangoor in 2006). Thanks, Christopher. Here is an article by Doug Hellmann about TurboGears WebServices, originally published Sept 2009 in Python Magazine: http://www.doughellmann.com/articles/pythonmagazine/features/building-soap-service//index.html From bradallen137 at gmail.com Tue Mar 2 18:09:51 2010 From: bradallen137 at gmail.com (Brad Allen) Date: Tue, 2 Mar 2010 11:09:51 -0600 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <22705760.56111267450344988.JavaMail.root@mail.corp> References: <3328574.56071267450245388.JavaMail.root@mail.corp> <22705760.56111267450344988.JavaMail.root@mail.corp> Message-ID: <4957f1ef1003020909v182c022bv23bc5d93ec414e38@mail.gmail.com> On Mon, Mar 1, 2010 at 7:32 AM, Eric Stein wrote: > At least in ZSI, there is too much marriage (IMHO) between the parser/serializer and the built-in web server. ?Perhaps this means I should be using a different library, but the investment made already is too much to waste switching to soaplib or similar. > > One of the biggest deficiencies I've observed in the python SOAP library space is documentation. ?For example, the latest version of ZSI (2.1-alpha1) does not appear to have a user's guide out yet. How active is ZSI? Is anyone maintaining it going forward? That latest release is from Nov 2007. As far as docs go, soaplib has the same problem. The docs are very limited and possibly outdated: http://trac.optio.webfactional.com/wiki/soaplib > On the subject of unifying the libraries into some common API: this doesn't seem productive to me. That might depend on whether we want to maintain multiple Python SOAP frameworks going forward. This community is small enough we may not be able to afford a lot of fragmentation. I would like to select one Python SOAP framework and focus efforts on adding docs, test coverage, continous integration servers, etc. Right now soaplib seems like a good starting point because there seem to be people actively developing (a lot of Github forks), and because at my employer we have gotten soaplib working and soon to move to production. However, I am hearing that suds is very active, and may be better than the soaplib client, so maybe it makes sense to retire the existing soaplib client and move to suds. Should I be considering ZSI as a SOAP server instead of soaplib? I have not investigated much about ZSI because I thought it was dead... From mdoar at pobox.com Tue Mar 2 18:54:27 2010 From: mdoar at pobox.com (Matt Doar) Date: Tue, 2 Mar 2010 17:54:27 +0000 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <4957f1ef1003020909v182c022bv23bc5d93ec414e38@mail.gmail.com> References: <3328574.56071267450245388.JavaMail.root@mail.corp> <22705760.56111267450344988.JavaMail.root@mail.corp> <4957f1ef1003020909v182c022bv23bc5d93ec414e38@mail.gmail.com> Message-ID: <7708e5011003020954r6e94aba9u9ffe3fa1dbe2df46@mail.gmail.com> I use SOAPpy (latest version is 3+ years old?) to connect to various web services such as JIRA. I like the flexibility of not having to create the transport objects first. The downside is less than helpful error messages. I've seen people doing this same thing using suds ~Matt On Tue, Mar 2, 2010 at 5:09 PM, Brad Allen wrote: > On Mon, Mar 1, 2010 at 7:32 AM, Eric Stein wrote: > > At least in ZSI, there is too much marriage (IMHO) between the > parser/serializer and the built-in web server. Perhaps this means I should > be using a different library, but the investment made already is too much to > waste switching to soaplib or similar. > > > > One of the biggest deficiencies I've observed in the python SOAP library > space is documentation. For example, the latest version of ZSI (2.1-alpha1) > does not appear to have a user's guide out yet. > > > How active is ZSI? Is anyone maintaining it going forward? That latest > release is from Nov 2007. > > As far as docs go, soaplib has the same problem. The docs are very > limited and possibly outdated: > > http://trac.optio.webfactional.com/wiki/soaplib > > > > On the subject of unifying the libraries into some common API: this > doesn't seem productive to me. > > That might depend on whether we want to maintain multiple Python SOAP > frameworks going forward. This community is small enough we may not be > able to afford a lot of fragmentation. > > I would like to select one Python SOAP framework and focus efforts on > adding docs, test coverage, continous integration servers, etc. Right > now soaplib seems like a good starting point because there seem to be > people actively developing (a lot of Github forks), and because at my > employer we have gotten soaplib working and soon to move to > production. > > However, I am hearing that suds is very active, and may be better than > the soaplib client, so maybe it makes sense to retire the existing > soaplib client and move to suds. > > Should I be considering ZSI as a SOAP server instead of soaplib? I > have not investigated much about ZSI because I thought it was dead... > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshua.gallagher at gmail.com Wed Mar 3 22:49:14 2010 From: joshua.gallagher at gmail.com (Joshua Gallagher) Date: Wed, 3 Mar 2010 13:49:14 -0800 Subject: [Soap-Python] The Python SOAP community: past, present, future In-Reply-To: <4957f1ef1003020909v182c022bv23bc5d93ec414e38@mail.gmail.com> References: <3328574.56071267450245388.JavaMail.root@mail.corp> <22705760.56111267450344988.JavaMail.root@mail.corp> <4957f1ef1003020909v182c022bv23bc5d93ec414e38@mail.gmail.com> Message-ID: <9bb4e5be1003031349w61dce9e6ib89ad2afc99c5e6@mail.gmail.com> I work in software QA for a small startup company. The product's management system is written in Java and exposes the internal management functions through SOAP. Those same internal functions are used by the CLI and GUI so we use SOAP extensively to conduct thorough regression testing. When I started developing these tests in 2008, I observed that there wasn't a lot of support for SOAP in the Python community. I just needed a client so my needs aren't extensive. I found ZSI to be reliable, well documented (don't look at the main docs--Holger Jouki's write-up is the best), and provided robust wsdl=>python conversion. It also works great on both Linux and Windows. I use the release 2.0 version as the 2.1 was (and still is) in alpha. While a new release hasn't come out in a while, the mailing list is fairly active and the project owner, Joshua Boverhof, is active and helpful. For what I need, ZSI works great. The biggest issue I have is that ZSI only supports SOAP 1.1, not SOAP 1.2. Also, while ZSI works great with Python 2.5, and less well with 2.6, it doesn't work at all with Python 3. Joshua On Tue, Mar 2, 2010 at 9:09 AM, Brad Allen wrote: > On Mon, Mar 1, 2010 at 7:32 AM, Eric Stein wrote: >> At least in ZSI, there is too much marriage (IMHO) between the parser/serializer and the built-in web server. ?Perhaps this means I should be using a different library, but the investment made already is too much to waste switching to soaplib or similar. >> >> One of the biggest deficiencies I've observed in the python SOAP library space is documentation. ?For example, the latest version of ZSI (2.1-alpha1) does not appear to have a user's guide out yet. > > > How active is ZSI? Is anyone maintaining it going forward? That latest > release is from Nov 2007. > > As far as docs go, soaplib has the same problem. The docs are very > limited and possibly outdated: > > http://trac.optio.webfactional.com/wiki/soaplib > > >> On the subject of unifying the libraries into some common API: this doesn't seem productive to me. > > That might depend on whether we want to maintain multiple Python SOAP > frameworks going forward. This community is small enough we may not be > able to afford a lot of fragmentation. > > I would like to select one Python SOAP framework and focus efforts on > adding docs, test coverage, continous integration servers, etc. Right > now soaplib seems like a good starting point because there seem to be > people actively developing (a lot of Github forks), and because at my > employer we have gotten soaplib working and soon to move to > production. > > However, I am hearing that suds is very active, and may be better than > the soaplib client, so maybe it makes sense to retire the existing > soaplib client and move to suds. > > Should I be considering ZSI as a SOAP server instead of soaplib? I > have not investigated much about ZSI because I thought it was dead... > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap > From jkp at kirkconsulting.co.uk Fri Mar 5 13:16:57 2010 From: jkp at kirkconsulting.co.uk (Jamie Kirkpatrick) Date: Fri, 5 Mar 2010 12:16:57 +0000 Subject: [Soap-Python] soaplib-0.8.1 on github In-Reply-To: <76C76A27-6641-48A9-86D6-692F549A2300@fnal.gov> References: <76C76A27-6641-48A9-86D6-692F549A2300@fnal.gov> Message-ID: <40ddf2481003050416o6775d225q8e075414cd3fdd0b@mail.gmail.com> Have you checked the latest source code in the git repo? It looks to me that this is already fixed... Let me know. Thanks On 3 March 2010 22:15, Randolph Reitz wrote: > The soaplib github page (http://wiki.github.com/jkp/soaplib/) list Prerequisites as python >=2.4. > > There are 2 lines in xml.py with conditional expression syntax that was introduced in Python 2.5 (PEP 308). ?Can you 'fix' these 2 lines so that soaplib is indeed compatible with python 2.4? > > Here are the lines (and my changes)... > > [nimi at nimisrv ~]$ diff ~/prod_2010_03_03/djroot/soaplib/xml.py /usr/lib/python2.4/site-packages/soaplib-0.8.1-py2.4.egg/soaplib > 36c36 > < ? ? ? ? ns = self.nsmap.get(key,'') > --- >> ? ? ? ? ns = self.nsmap[key] if key in self.nsmap else '' > 64,68c64 > < ? ? if default_ns is not None: > < ? ? ? ? namespace_map = { None: default_ns } > < ? ? else : > < ? ? ? ? namespace_map = {} > < > --- >> ? ? namespace_map = { None: default_ns } if default_ns is not None else {} > > > My server is stuck with python 2.4. > > Thanks, > Randy > > -- Jamie Kirkpatrick 07818 422311 From jkp at kirkconsulting.co.uk Fri Mar 5 17:17:20 2010 From: jkp at kirkconsulting.co.uk (Jamie Kirkpatrick) Date: Fri, 5 Mar 2010 16:17:20 +0000 Subject: [Soap-Python] soaplib-0.8.1 on github In-Reply-To: <73D31575-E7DC-44BC-A8DA-A5BA29AC3140@fnal.gov> References: <76C76A27-6641-48A9-86D6-692F549A2300@fnal.gov> <40ddf2481003050416o6775d225q8e075414cd3fdd0b@mail.gmail.com> <73D31575-E7DC-44BC-A8DA-A5BA29AC3140@fnal.gov> Message-ID: <40ddf2481003050817k385ce727t6972861a98ef659b@mail.gmail.com> Hi Randy The fix is not in the 0.8.1 tarball: its in the git HEAD. It will be in the next release but until then you might want to grab the latest source code directly from Git and use that. Jamie On 5 March 2010 14:57, Randolph Reitz wrote: > I find soaplib-0.8.1.tar (2009-07-14) on http://github.com/jkp/soaplib/downloads. ?After unwinding the tar ball... > > [rreitz at nimisrv soaplib]$ ls > client.py ? ? ? etimport.py ?__init__.py ?service.py ?util.py ? ? ? xml.py > easy_client.py ?ext ? ? ? ? ?serializers ?soap.py ? ? wsgi_soap.py > [rreitz at nimisrv soaplib]$ python -i xml.py > ?File "xml.py", line 36 > ? ?ns = self.nsmap[key] if key in self.nsmap else '' > ? ? ? ? ? ? ? ? ? ? ? ? ?^ > SyntaxError: invalid syntax > > where > > [rreitz at nimisrv soaplib]$ python -V > Python 2.4.3 > > > Randy > > On Mar 5, 2010, at 6:16 AM, Jamie Kirkpatrick wrote: > >> Have you checked the latest source code in the git repo? ?It looks to >> me that this is already fixed... >> >> Let me know. >> >> Thanks >> >> On 3 March 2010 22:15, Randolph Reitz wrote: >>> The soaplib github page (http://wiki.github.com/jkp/soaplib/) list Prerequisites as python >=2.4. >>> >>> There are 2 lines in xml.py with conditional expression syntax that was introduced in Python 2.5 (PEP 308). ?Can you 'fix' these 2 lines so that soaplib is indeed compatible with python 2.4? >>> >>> Here are the lines (and my changes)... >>> >>> [nimi at nimisrv ~]$ diff ~/prod_2010_03_03/djroot/soaplib/xml.py /usr/lib/python2.4/site-packages/soaplib-0.8.1-py2.4.egg/soaplib >>> 36c36 >>> < ? ? ? ? ns = self.nsmap.get(key,'') >>> --- >>>> ? ? ? ? ns = self.nsmap[key] if key in self.nsmap else '' >>> 64,68c64 >>> < ? ? if default_ns is not None: >>> < ? ? ? ? namespace_map = { None: default_ns } >>> < ? ? else : >>> < ? ? ? ? namespace_map = {} >>> < >>> --- >>>> ? ? namespace_map = { None: default_ns } if default_ns is not None else {} >>> >>> >>> My server is stuck with python 2.4. >>> >>> Thanks, >>> Randy >>> >>> >> >> >> >> -- >> Jamie Kirkpatrick >> 07818 422311 > > -- Jamie Kirkpatrick 07818 422311 From bradallen137 at gmail.com Fri Mar 5 19:35:03 2010 From: bradallen137 at gmail.com (Brad Allen) Date: Fri, 5 Mar 2010 12:35:03 -0600 Subject: [Soap-Python] soaplib-0.8.1 on github In-Reply-To: <40ddf2481003050817k385ce727t6972861a98ef659b@mail.gmail.com> References: <76C76A27-6641-48A9-86D6-692F549A2300@fnal.gov> <40ddf2481003050416o6775d225q8e075414cd3fdd0b@mail.gmail.com> <73D31575-E7DC-44BC-A8DA-A5BA29AC3140@fnal.gov> <40ddf2481003050817k385ce727t6972861a98ef659b@mail.gmail.com> Message-ID: <4957f1ef1003051035u75468db4i7c374f1440fad991@mail.gmail.com> On Fri, Mar 5, 2010 at 10:17 AM, Jamie Kirkpatrick wrote: > Hi Randy > > The fix is not in the 0.8.1 tarball: its in the git HEAD. ? It will be > in the next release but until then you might want to grab the latest > source code directly from Git and use that. Jamie, when is the next release planned? I am wondering if anyone is interested in reviewing the changes from cuker to determine if they should be merged. (I have not looked at those, so I don't know what they are about, but have heard that is a significant branch) From rreitz at fnal.gov Fri Mar 5 15:57:43 2010 From: rreitz at fnal.gov (Randolph Reitz) Date: Fri, 05 Mar 2010 08:57:43 -0600 Subject: [Soap-Python] soaplib-0.8.1 on github In-Reply-To: <40ddf2481003050416o6775d225q8e075414cd3fdd0b@mail.gmail.com> References: <76C76A27-6641-48A9-86D6-692F549A2300@fnal.gov> <40ddf2481003050416o6775d225q8e075414cd3fdd0b@mail.gmail.com> Message-ID: <73D31575-E7DC-44BC-A8DA-A5BA29AC3140@fnal.gov> I find soaplib-0.8.1.tar (2009-07-14) on http://github.com/jkp/soaplib/downloads. After unwinding the tar ball... [rreitz at nimisrv soaplib]$ ls client.py etimport.py __init__.py service.py util.py xml.py easy_client.py ext serializers soap.py wsgi_soap.py [rreitz at nimisrv soaplib]$ python -i xml.py File "xml.py", line 36 ns = self.nsmap[key] if key in self.nsmap else '' ^ SyntaxError: invalid syntax where [rreitz at nimisrv soaplib]$ python -V Python 2.4.3 Randy On Mar 5, 2010, at 6:16 AM, Jamie Kirkpatrick wrote: > Have you checked the latest source code in the git repo? It looks to > me that this is already fixed... > > Let me know. > > Thanks > > On 3 March 2010 22:15, Randolph Reitz wrote: >> The soaplib github page (http://wiki.github.com/jkp/soaplib/) list Prerequisites as python >=2.4. >> >> There are 2 lines in xml.py with conditional expression syntax that was introduced in Python 2.5 (PEP 308). Can you 'fix' these 2 lines so that soaplib is indeed compatible with python 2.4? >> >> Here are the lines (and my changes)... >> >> [nimi at nimisrv ~]$ diff ~/prod_2010_03_03/djroot/soaplib/xml.py /usr/lib/python2.4/site-packages/soaplib-0.8.1-py2.4.egg/soaplib >> 36c36 >> < ns = self.nsmap.get(key,'') >> --- >>> ns = self.nsmap[key] if key in self.nsmap else '' >> 64,68c64 >> < if default_ns is not None: >> < namespace_map = { None: default_ns } >> < else : >> < namespace_map = {} >> < >> --- >>> namespace_map = { None: default_ns } if default_ns is not None else {} >> >> >> My server is stuck with python 2.4. >> >> Thanks, >> Randy >> >> > > > > -- > Jamie Kirkpatrick > 07818 422311 From binbrain at gmail.com Wed Mar 17 19:35:36 2010 From: binbrain at gmail.com (Jim Pharis) Date: Wed, 17 Mar 2010 14:35:36 -0400 Subject: [Soap-Python] soaplib using lxml.XMLID which returns nothing Message-ID: <77f231801003171135m7d10dd8cs6e99e634c4d3715@mail.gmail.com> SOAP packets don't have a id= attribute necessarily. In soaplib/soap.py the from_xml def calls ElementTree.XMLID (which is actually lxml.XMLID) which searches for the id attribute in the XML to build the dict. This returns nothing. Am I seeing this problem wrong. - Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From binbrain at gmail.com Wed Mar 24 15:57:47 2010 From: binbrain at gmail.com (Jim Pharis) Date: Wed, 24 Mar 2010 10:57:47 -0400 Subject: [Soap-Python] suds doesn't work w/soaplib Message-ID: <77f231801003240757g67cbc1f2y2f5bb6cea1e89b41@mail.gmail.com> I tried asking the below question earlier and didn't get any feedback. In essence, soaplib seems to have an esoteric way of parsing soap packets that isn't standard. The problem is that soaplib looks for an id attribute on the elements in the SOAP packet. Problem explained in more detail in the below message. http://mail.python.org/pipermail/soap/2010-March/000017.html So perhaps I'll ask a more general question that might raise some eyebrows. Why don't suds and soaplib work together? hello world example right from soaplib's site =============================== from soaplib.wsgi_soap import SimpleWSGISoapApp from soaplib.service import soapmethod from soaplib.serializers.primitive import String, Integer, Array class HelloWorldService(SimpleWSGISoapApp): @soapmethod(String,Integer,_returns=Array(String)) def say_hello(self,name,times): results = [] for i in range(0,times): results.append('Hello, %s'%name) return results if __name__=='__main__': from cherrypy.wsgiserver import CherryPyWSGIServer server = CherryPyWSGIServer(('localhost',7789),HelloWorldService()) server.start() simple suds client to work with it ======================== from suds.client import Client wsdl = "http://localhost:7789/wsdl" client = Client(wsdl) hi = client.factory.create('say_hello') hi.name = "Bob" hi.times = 2 client.service.say_hello(hi) Result ==== C:\>python test_helloworld.py No handlers could be found for logger "suds.client" Traceback (most recent call last): File "test_helloworld.py", line 9, in ? client.service.say_hello(hi) File "build\bdist.win32\egg\suds\client.py", line 535, in __call__ File "build\bdist.win32\egg\suds\client.py", line 595, in invoke File "build\bdist.win32\egg\suds\client.py", line 630, in send File "build\bdist.win32\egg\suds\client.py", line 681, in failed File "build\bdist.win32\egg\suds\bindings\binding.py", line 235, in get_fault suds.WebFault: Server raised fault: 'range() integer end argument expected, got NoneType.' This occurs because times is None because soaplib couldn't find the elements because they have no id attribute in the tags in the SOAP packet. - Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From burak.arslan at arskom.com.tr Wed Mar 24 16:09:06 2010 From: burak.arslan at arskom.com.tr (Burak Arslan) Date: Wed, 24 Mar 2010 17:09:06 +0200 Subject: [Soap-Python] suds doesn't work w/soaplib In-Reply-To: <77f231801003240757g67cbc1f2y2f5bb6cea1e89b41@mail.gmail.com> References: <77f231801003240757g67cbc1f2y2f5bb6cea1e89b41@mail.gmail.com> Message-ID: <4BAA2B12.5090502@arskom.com.tr> On 03/24/10 16:57, Jim Pharis wrote: > So perhaps I'll ask a more general question that might raise some > eyebrows. Why don't suds and soaplib work together? they do, many of us are using them together. however if you think you've found a glitch, patches to the one or both of the packages would be welcome. burak From burak.arslan at arskom.com.tr Wed Mar 24 17:02:15 2010 From: burak.arslan at arskom.com.tr (Burak Arslan) Date: Wed, 24 Mar 2010 18:02:15 +0200 Subject: [Soap-Python] suds doesn't work w/soaplib In-Reply-To: <77f231801003240813l6c689c6dr41ec0e9861220f5c@mail.gmail.com> References: <77f231801003240757g67cbc1f2y2f5bb6cea1e89b41@mail.gmail.com> <4BAA2B12.5090502@arskom.com.tr> <77f231801003240813l6c689c6dr41ec0e9861220f5c@mail.gmail.com> Message-ID: <4BAA3787.4020002@arskom.com.tr> On 03/24/10 17:13, Jim Pharis wrote: > Hey Burak, thanks for the feedback. Can you provide a simple working > client to give me something to go on? Do you have to do anything > special on the suds side to work with soaplib, or is it working right > out of the box for you without any special modifications or > considerations? > here's a sample (yes, just 3 lines): =========== from suds.client import Client client= Client("http://localhost:7789/?wsdl") print client.service.say_hello("punk",5) =========== here's the output: No handlers could be found for logger "suds.umx.typed" (stringArray){ _type = "tns:stringArray" string[] = "Hello, punk", "Hello, punk", "Hello, punk", "Hello, punk", "Hello, punk", } hth burak From binbrain at gmail.com Wed Mar 24 18:11:50 2010 From: binbrain at gmail.com (Jim Pharis) Date: Wed, 24 Mar 2010 13:11:50 -0400 Subject: [Soap-Python] suds doesn't work w/soaplib In-Reply-To: <4BAA2B12.5090502@arskom.com.tr> References: <77f231801003240757g67cbc1f2y2f5bb6cea1e89b41@mail.gmail.com> <4BAA2B12.5090502@arskom.com.tr> Message-ID: <77f231801003241011t1e6af080m268f80844d954413@mail.gmail.com> Interesting. It looks like you get different results with suds if you pass params right to the service vs creating the complextType with the factory.create method. The params are actually being passed now. Am I creating my complexType wrong or something... No suds factory '\n \n \n \n punk\n 2\n \n \n' Using suds factory create '\n \n \n \n \n Punk\n 3\n \n \n \n \n' On Wed, Mar 24, 2010 at 11:48 AM, Burak Arslan wrote: > On 03/24/10 17:13, Jim Pharis wrote: > >> Hey Burak, thanks for the feedback. Can you provide a simple working >> client to give me something to go on? Do you have to do anything special on >> the suds side to work with soaplib, or is it working right out of the box >> for you without any special modifications or considerations? >> >> > here's a sample (yes, just 3 lines): > > > =========== > > from suds.client import Client > > client= Client("http://localhost:7789/?wsdl") > print client.service.say_hello("punk",5) > > =========== > > here's the output: > > No handlers could be found for logger "suds.umx.typed" > (stringArray){ > _type = "tns:stringArray" > string[] = > "Hello, punk", > "Hello, punk", > "Hello, punk", > "Hello, punk", > "Hello, punk", > } > > > hth > burak > On Wed, Mar 24, 2010 at 11:09 AM, Burak Arslan wrote: > On 03/24/10 16:57, Jim Pharis wrote: > >> So perhaps I'll ask a more general question that might raise some >> eyebrows. Why don't suds and soaplib work together? >> > > they do, many of us are using them together. however if you think you've > found a glitch, patches to the one or both of the packages would be welcome. > > burak > -------------- next part -------------- An HTML attachment was scrubbed... URL: From binbrain at gmail.com Wed Mar 24 18:22:33 2010 From: binbrain at gmail.com (Jim Pharis) Date: Wed, 24 Mar 2010 13:22:33 -0400 Subject: [Soap-Python] suds doesn't work w/soaplib In-Reply-To: <77f231801003241011t1e6af080m268f80844d954413@mail.gmail.com> References: <77f231801003240757g67cbc1f2y2f5bb6cea1e89b41@mail.gmail.com> <4BAA2B12.5090502@arskom.com.tr> <77f231801003241011t1e6af080m268f80844d954413@mail.gmail.com> Message-ID: <77f231801003241022t4df6e12ck70d05ec7919baa98@mail.gmail.com> Another note, it looks like XMLID call returns nothing for either SOAP packet, and since I know the 1st SOAP packet below gets the params to my method correctly, the values must be extracted from somewhere else. Guess that can be eliminated as a problem. On Wed, Mar 24, 2010 at 1:11 PM, Jim Pharis wrote: > Interesting. It looks like you get different results with suds if you pass > params right to the service vs creating the complextType with the > factory.create method. The params are actually being passed now. Am I > creating my complexType wrong or something... > > No suds factory > > ' xmlns:xsi="h > ttp://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV=" > http://schemas.xmlsoap > .org/soap/envelope/">\n \n \n > _hello>\n punk\n 2\n > hello>\n \n' > > Using suds factory create > > ' xmlns:xsi="h > ttp://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV=" > http://schemas.xmlsoap > .org/soap/envelope/">\n \n \n > _hello>\n \n Punk\n > 3 imes>\n \n \n \n > V:Body>\n' > > > On Wed, Mar 24, 2010 at 11:48 AM, Burak Arslan > wrote: > >> On 03/24/10 17:13, Jim Pharis wrote: >> >>> Hey Burak, thanks for the feedback. Can you provide a simple working >>> client to give me something to go on? Do you have to do anything special on >>> the suds side to work with soaplib, or is it working right out of the box >>> for you without any special modifications or considerations? >>> >>> >> here's a sample (yes, just 3 lines): >> >> >> =========== >> >> from suds.client import Client >> >> client= Client("http://localhost:7789/?wsdl") >> print client.service.say_hello("punk",5) >> >> =========== >> >> here's the output: >> >> No handlers could be found for logger "suds.umx.typed" >> (stringArray){ >> _type = "tns:stringArray" >> string[] = >> "Hello, punk", >> "Hello, punk", >> "Hello, punk", >> "Hello, punk", >> "Hello, punk", >> } >> >> >> hth >> burak >> > > > > On Wed, Mar 24, 2010 at 11:09 AM, Burak Arslan > wrote: > >> On 03/24/10 16:57, Jim Pharis wrote: >> >>> So perhaps I'll ask a more general question that might raise some >>> eyebrows. Why don't suds and soaplib work together? >>> >> >> they do, many of us are using them together. however if you think you've >> found a glitch, patches to the one or both of the packages would be welcome. >> >> burak >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: