From kevin.s.anthony at gmail.com Mon Jan 3 23:02:34 2011 From: kevin.s.anthony at gmail.com (Kevin Anthony) Date: Mon, 3 Jan 2011 17:02:34 -0500 Subject: [Soap-Python] Running a SOAPpy server in a thread Message-ID: I'm writing a SOAPpy server in a thread, and having a problem handling the exiting What happens is handle_request() blocks until a request comes in. so the thread exit's normally once a request comes in, but the server could sit running for hours before a request comes in. is there a non-blocking method i can call before i call handle_request I've played around with socket timeouts but haven't had much success. is there a way to do this? here's my code current code: def run(self): self._server = SOAPpy.SOAPServer(self._addr) self._server.registerObject(self,self._NS) logging.info("Starting Soap Server (ctrl+c to stop)") while not self._stopevent.isSet(): self._server.handle_request() self._stopevent.wait(self._sleepPeriod) def join(self, timeout=None): self._stopevent.set() threading.Thread.join(self, timeout) self._server.server_close() logging.warning("Exiting Thread :%s" %(self.getName())) -- Thanks Kevin Anthony www.NoSideRacing.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcus at priesch.priv.at Wed Jan 5 08:18:06 2011 From: marcus at priesch.priv.at (Marcus Priesch) Date: Wed, 05 Jan 2011 08:18:06 +0100 Subject: [Soap-Python] Running a SOAPpy server in a thread In-Reply-To: References: Message-ID: <1294211886.4703.20.camel@pr-laptop> Hi Kevin, why do you want to exit the thread on demand ? wouldnt t = threading.Thread (target = self._server.server_forever) t.daemon = True t.start () be sufficient (i dont know exactly if there is a server_forever method but it would simply be a while True: handle_request() loop) ? however, as far as i understand your code you are witing after each handled request ?!? regards, m. Am Montag, den 03.01.2011, 17:02 -0500 schrieb Kevin Anthony: > I'm writing a SOAPpy server in a thread, and having a problem handling > the exiting > > > What happens is handle_request() blocks until a request comes in. so > the thread exit's normally once a request comes in, but the server > could sit running for hours before a request comes in. > is there a non-blocking method i can call before i call handle_request > > > I've played around with socket timeouts but haven't had much success. > is there a way to do this? > > > here's my code current code: > > > def run(self): > self._server = SOAPpy.SOAPServer(self._addr) > self._server.registerObject(self,self._NS) > logging.info("Starting Soap Server (ctrl+c to stop)") > while not self._stopevent.isSet(): > self._server.handle_request() > self._stopevent.wait(self._sleepPeriod) > > > def join(self, timeout=None): > self._stopevent.set() > threading.Thread.join(self, timeout) > self._server.server_close() > logging.warning("Exiting Thread :%s" > %(self.getName())) > > > > -- > Thanks > Kevin Anthony > www.NoSideRacing.com > 732.793.3473 > > > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap From kevin.s.anthony at gmail.com Wed Jan 5 19:01:09 2011 From: kevin.s.anthony at gmail.com (Kevin Anthony) Date: Wed, 5 Jan 2011 13:01:09 -0500 Subject: [Soap-Python] Running a SOAPpy server in a thread In-Reply-To: <1294211886.4703.20.camel@pr-laptop> References: <1294211886.4703.20.camel@pr-laptop> Message-ID: I need to be able to start and stop the soap server programmatically. There doesn't seem to be a way to stop serve_forever without killing the entire program. On Wed, Jan 5, 2011 at 2:18 AM, Marcus Priesch wrote: > > Hi Kevin, > > why do you want to exit the thread on demand ? > > wouldnt > > ?t = threading.Thread (target = self._server.server_forever) > ?t.daemon = True > ?t.start () > > be sufficient (i dont know exactly if there is a server_forever method > but it would simply be a while True: handle_request() loop) ? > > however, as far as i understand your code you are witing after each > handled request ?!? > > regards, > m. > > Am Montag, den 03.01.2011, 17:02 -0500 schrieb Kevin Anthony: > > I'm writing a SOAPpy server in a thread, and having a problem handling > > the exiting > > > > > > What happens is handle_request() blocks until a request comes in. so > > the thread exit's normally once a request comes in, but the server > > could sit running for hours before a request comes in. > > is there a non-blocking method i can call before i call handle_request > > > > > > I've played around with socket timeouts but haven't had much success. > > ?is there a way to do this? > > > > > > here's my code current code: > > > > > > ? ? ? ? def run(self): > > ? ? ? ? ? ? ? ? self._server = SOAPpy.SOAPServer(self._addr) > > ? ? ? ? ? ? ? ? self._server.registerObject(self,self._NS) > > ? ? ? ? ? ? ? ? logging.info("Starting Soap Server (ctrl+c to stop)") > > ? ? ? ? ? ? ? ? while not self._stopevent.isSet(): > > ? ? ? ? ? ? ? ? ? ? ? ? self._server.handle_request() > > ? ? ? ? ? ? ? ? ? ? ? ? self._stopevent.wait(self._sleepPeriod) > > > > > > ? ? ? ? def join(self, timeout=None): > > ? ? ? ? ? ? ? ? self._stopevent.set() > > ? ? ? ? ? ? ? ? threading.Thread.join(self, timeout) > > ? ? ? ? ? ? ? ? self._server.server_close() > > ? ? ? ? ? ? ? ? logging.warning("Exiting Thread :%s" > > %(self.getName())) > > > > > > > > -- > > Thanks > > Kevin Anthony > > www.NoSideRacing.com > > 732.793.3473 > > > > > > _______________________________________________ > > Soap mailing list > > Soap at python.org > > http://mail.python.org/mailman/listinfo/soap > > > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap -- Thanks Kevin Anthony www.NoSideRacing.com 732.793.3473 From marcus at priesch.priv.at Wed Jan 5 20:41:06 2011 From: marcus at priesch.priv.at (Marcus Priesch) Date: Wed, 05 Jan 2011 20:41:06 +0100 Subject: [Soap-Python] Running a SOAPpy server in a thread In-Reply-To: References: <1294211886.4703.20.camel@pr-laptop> Message-ID: <1294256466.4703.104.camel@pr-laptop> Am Mittwoch, den 05.01.2011, 13:01 -0500 schrieb Kevin Anthony: > I need to be able to start and stop the soap server programmatically. > > There doesn't seem to be a way to stop serve_forever without killing > the entire program. yes, there is no way to kill a thread :( ... but maybe you would like to join in on the multiprocessing module :) its usage is nearly identical - as you can always kill a process ... :) have fun, m. > > On Wed, Jan 5, 2011 at 2:18 AM, Marcus Priesch wrote: > > > > Hi Kevin, > > > > why do you want to exit the thread on demand ? > > > > wouldnt > > > > t = threading.Thread (target = self._server.server_forever) > > t.daemon = True > > t.start () > > > > be sufficient (i dont know exactly if there is a server_forever method > > but it would simply be a while True: handle_request() loop) ? > > > > however, as far as i understand your code you are witing after each > > handled request ?!? > > > > regards, > > m. > > > > Am Montag, den 03.01.2011, 17:02 -0500 schrieb Kevin Anthony: > > > I'm writing a SOAPpy server in a thread, and having a problem handling > > > the exiting > > > > > > > > > What happens is handle_request() blocks until a request comes in. so > > > the thread exit's normally once a request comes in, but the server > > > could sit running for hours before a request comes in. > > > is there a non-blocking method i can call before i call handle_request > > > > > > > > > I've played around with socket timeouts but haven't had much success. > > > is there a way to do this? > > > > > > > > > here's my code current code: > > > > > > > > > def run(self): > > > self._server = SOAPpy.SOAPServer(self._addr) > > > self._server.registerObject(self,self._NS) > > > logging.info("Starting Soap Server (ctrl+c to stop)") > > > while not self._stopevent.isSet(): > > > self._server.handle_request() > > > self._stopevent.wait(self._sleepPeriod) > > > > > > > > > def join(self, timeout=None): > > > self._stopevent.set() > > > threading.Thread.join(self, timeout) > > > self._server.server_close() > > > logging.warning("Exiting Thread :%s" > > > %(self.getName())) > > > > > > > > > > > > -- > > > Thanks > > > Kevin Anthony > > > www.NoSideRacing.com > > > 732.793.3473 > > > > > > > > > _______________________________________________ > > > Soap mailing list > > > Soap at python.org > > > http://mail.python.org/mailman/listinfo/soap > > > > > > _______________________________________________ > > Soap mailing list > > Soap at python.org > > http://mail.python.org/mailman/listinfo/soap > > > > -- > Thanks > Kevin Anthony > www.NoSideRacing.com > 732.793.3473 From chris at sydneysys.com Thu Jan 20 23:53:25 2011 From: chris at sydneysys.com (Chris Austin) Date: Thu, 20 Jan 2011 16:53:25 -0600 Subject: [Soap-Python] Soaplib beat1 released into the wild Message-ID: We are pleased to announce 2.1.0-beta1 of soaplib. This introduces significant API changes since the 2.1.0-alpha released in Sept 2010. This release also marks the transition to new maintainers (Brad Allen and Chris Austin), and a new repository location indicated on the new PyPI record (?https://github.com/soapapistas/soaplib). Soaplib is an easy to use Python library for publishing SOAP web services using WSDL 1.1 standard, and answering SOAP 1.1 requests. With a very small amount of code, soaplib allows you to write and deploy useful web services. It is designed to be web framework agnostic, with bundled examples of use with specific servers (Zope2, Twisted, CherryPy, WSGI). Soaplib is fast: it relies on lxml for performance intensive aspects such as XML parsing, validation, and namespace maps. We'd like to thank ZeOmega (my employer) for sponsoring the work done by myself, Brad Allen and many others to help keep soaplib moving. This release includes many bug fixes and API changes designed to improve readability. Highlights of this release are: +Now we have Sphinx docs with working examples: http://soapapistas.github.com/soaplib/2_0/ +The Serializer types have been renamed to Model to better fit their use and similarity to ?active record? declarative models seen in ORMs. +Standalone xsd generation for ClassSerializer objects has been added. This allows soaplib to be used to define generic XML schemas, without SOAP artifacts. +Annotation Tags for primitive Models has been added. +Custom PortType(s) and Service(s) are now supported. +WSDL generation has been moved out of the Application class and is now handled by a standalone WSDL class. +The soaplib client has been re-written after having been dropped from recent releases. It follows the suds API but is based on lxml for better performance. WARNING: the soaplib client is not well-tested and future support is tentative dependent on community response. ? It's current location is in a seperate repo at https://github.com/soaplib/soaplib.client +0mq support has been added via a service and client. Again, this is experimental and not fully supported at this point. +Increased test coverage for soaplib and supported servers. Upcoming soaplib organization releases: Tres Seaver has built a WSRP (Web Services for Remote Portlets) library called wsrplib on top of soaplib. This library is being release shortly under the soaplib organization and can currently be found at https://github.com/soaplib/wsrplib . Many of the recent API additions to soaplib were driven by this effort. Once again, this work would not have been possible without the sponsorship of ZeOmega. We are interested in establishing a robust community process to encourage adoption and contribution. Please let us know if you have input on how we can get there; the goal is to provide a solid end-to-end choice for working with SOAP using Python. Additional thanks go out to everyone who has made suggestions, rants, and most importantly submitted any type of bugfix. From bradallen137 at gmail.com Fri Jan 21 00:14:00 2011 From: bradallen137 at gmail.com (Brad Allen) Date: Thu, 20 Jan 2011 17:14:00 -0600 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: Let's not forget to include Burak in the thanks as well. Even though he is not currently available to work on soaplib, he did a huge amount of work in the leadup to 2.0 over the last few months. We should also thank Tres Seaver at Agendaless Computing who while working on wsrplib, provided invaluable input for improving soaplib. We'll make sure to include that in the Python-general announcement. On Thu, Jan 20, 2011 at 4:53 PM, Chris Austin wrote: > We are pleased to announce 2.1.0-beta1 of soaplib. This introduces > significant API changes since the 2.1.0-alpha released in Sept 2010. > > This release also marks the transition to new maintainers (Brad Allen > and Chris Austin), and a new repository location indicated on the new > PyPI record (?https://github.com/soapapistas/soaplib). > > Soaplib is an easy to use Python library for publishing SOAP web > services using WSDL 1.1 standard, and answering SOAP 1.1 requests. > With a very small amount of code, soaplib allows you to write and > deploy useful web services. It is designed to be web framework > agnostic, with bundled examples of use with specific servers (Zope2, > Twisted, CherryPy, WSGI). > > Soaplib is fast: it relies on lxml for performance intensive aspects > such as XML parsing, validation, and namespace maps. > > > We'd like to thank ZeOmega (my employer) for sponsoring the work done > by myself, Brad Allen and many others to help keep soaplib moving. > > This release includes many bug fixes and API changes designed to > improve readability. > > Highlights of this release are: > > +Now we have Sphinx docs with working examples: > http://soapapistas.github.com/soaplib/2_0/ > +The Serializer types have been renamed to Model to better fit their > use and similarity to ?active record? declarative models seen in ORMs. > +Standalone xsd generation for ClassSerializer objects has been added. > This allows soaplib to be used to define generic XML schemas, without > SOAP artifacts. > +Annotation Tags for primitive Models has been added. > +Custom PortType(s) and Service(s) are now supported. > +WSDL generation has been moved out of the Application class and is > now handled by a standalone WSDL class. > +The soaplib client has been re-written after having been dropped from > recent releases. It follows the suds API but is based on lxml for > better performance. WARNING: the soaplib client is not well-tested and > future support is tentative dependent on community response. ? It's > current location is in a seperate repo at > https://github.com/soaplib/soaplib.client > +0mq support has been added via a service and client. ?Again, this is > experimental and not fully supported at this point. > +Increased test coverage for soaplib and supported servers. > > Upcoming soaplib organization releases: > > Tres Seaver has built a WSRP (Web Services for Remote Portlets) > library called wsrplib on top of soaplib. ?This library is being > release shortly under the soaplib organization and can currently be > found at https://github.com/soaplib/wsrplib . ?Many of the recent API > additions to soaplib were driven by this effort. ?Once again, this > work would not have been possible without the sponsorship of ZeOmega. > > > We are interested in establishing a robust community process to > encourage adoption and contribution. Please let us know if you have > input on how we can get there; the goal is to provide a solid > end-to-end choice for working with SOAP using Python. > > > Additional thanks go out to everyone who has made suggestions, rants, > and most importantly submitted any type of bugfix. > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap > From ovnicraft at gmail.com Fri Jan 21 00:26:18 2011 From: ovnicraft at gmail.com (Ovnicraft) Date: Thu, 20 Jan 2011 18:26:18 -0500 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: On Thu, Jan 20, 2011 at 5:53 PM, Chris Austin wrote: > We are pleased to announce 2.1.0-beta1 of soaplib. This introduces > significant API changes since the 2.1.0-alpha released in Sept 2010. > > This release also marks the transition to new maintainers (Brad Allen > and Chris Austin), and a new repository location indicated on the new > PyPI record ( https://github.com/soapapistas/soaplib). > > Soaplib is an easy to use Python library for publishing SOAP web > services using WSDL 1.1 standard, and answering SOAP 1.1 requests. > With a very small amount of code, soaplib allows you to write and > deploy useful web services. It is designed to be web framework > agnostic, with bundled examples of use with specific servers (Zope2, > Twisted, CherryPy, WSGI). > > Soaplib is fast: it relies on lxml for performance intensive aspects > such as XML parsing, validation, and namespace maps. > > > We'd like to thank ZeOmega (my employer) for sponsoring the work done > by myself, Brad Allen and many others to help keep soaplib moving. > > This release includes many bug fixes and API changes designed to > improve readability. > > Highlights of this release are: > > +Now we have Sphinx docs with working examples: > http://soapapistas.github.com/soaplib/2_0/ This page give me 404. > > +The Serializer types have been renamed to Model to better fit their > use and similarity to ?active record? declarative models seen in ORMs. > +Standalone xsd generation for ClassSerializer objects has been added. > This allows soaplib to be used to define generic XML schemas, without > SOAP artifacts. > +Annotation Tags for primitive Models has been added. > +Custom PortType(s) and Service(s) are now supported. > +WSDL generation has been moved out of the Application class and is > now handled by a standalone WSDL class. > +The soaplib client has been re-written after having been dropped from > recent releases. It follows the suds API but is based on lxml for > better performance. WARNING: the soaplib client is not well-tested and > future support is tentative dependent on community response. It's > current location is in a seperate repo at > https://github.com/soaplib/soaplib.client Believe in suds. IMHO more effort can applied in soaplib as server > > +0mq support has been added via a service and client. Again, this is > experimental and not fully supported at this point. > +Increased test coverage for soaplib and supported servers. > > Upcoming soaplib organization releases: > > Tres Seaver has built a WSRP (Web Services for Remote Portlets) > library called wsrplib on top of soaplib. This library is being > release shortly under the soaplib organization and can currently be > found at https://github.com/soaplib/wsrplib . Many of the recent API > additions to soaplib were driven by this effort. Once again, this > work would not have been possible without the sponsorship of ZeOmega. > > > We are interested in establishing a robust community process to > encourage adoption and contribution. Please let us know if you have > input on how we can get there; the goal is to provide a solid > end-to-end choice for working with SOAP using Python. > > > Additional thanks go out to everyone who has made suggestions, rants, > and most importantly submitted any type of bugfix. > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap > -- Cristian Salamea @ovnicraft -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at sydneysys.com Fri Jan 21 00:32:56 2011 From: chris at sydneysys.com (Chris Austin) Date: Thu, 20 Jan 2011 17:32:56 -0600 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: Thank you! The correct link is http://soaplib.github.com/soaplib/2_0/ - Show quoted text - On Thu, Jan 20, 2011 at 5:26 PM, Ovnicraft wrote: > > > On Thu, Jan 20, 2011 at 5:53 PM, Chris Austin wrote: >> >> We are pleased to announce 2.1.0-beta1 of soaplib. This introduces >> significant API changes since the 2.1.0-alpha released in Sept 2010. >> >> This release also marks the transition to new maintainers (Brad Allen >> and Chris Austin), and a new repository location indicated on the new >> PyPI record (?https://github.com/soapapistas/soaplib). >> >> Soaplib is an easy to use Python library for publishing SOAP web >> services using WSDL 1.1 standard, and answering SOAP 1.1 requests. >> With a very small amount of code, soaplib allows you to write and >> deploy useful web services. It is designed to be web framework >> agnostic, with bundled examples of use with specific servers (Zope2, >> Twisted, CherryPy, WSGI). >> >> Soaplib is fast: it relies on lxml for performance intensive aspects >> such as XML parsing, validation, and namespace maps. >> >> >> We'd like to thank ZeOmega (my employer) for sponsoring the work done >> by myself, Brad Allen and many others to help keep soaplib moving. >> >> This release includes many bug fixes and API changes designed to >> improve readability. >> >> Highlights of this release are: >> >> +Now we have Sphinx docs with working examples: >> http://soapapistas.github.com/soaplib/2_0/ > > This page give me 404. > >> >> +The Serializer types have been renamed to Model to better fit their >> use and similarity to ?active record? declarative models seen in ORMs. >> +Standalone xsd generation for ClassSerializer objects has been added. >> This allows soaplib to be used to define generic XML schemas, without >> SOAP artifacts. >> +Annotation Tags for primitive Models has been added. >> +Custom PortType(s) and Service(s) are now supported. >> +WSDL generation has been moved out of the Application class and is >> now handled by a standalone WSDL class. >> +The soaplib client has been re-written after having been dropped from >> recent releases. It follows the suds API but is based on lxml for >> better performance. WARNING: the soaplib client is not well-tested and >> future support is tentative dependent on community response. ? It's >> current location is in a seperate repo at >> https://github.com/soaplib/soaplib.client > > Believe in suds. IMHO more effort can applied in soaplib as server >> >> +0mq support has been added via a service and client. ?Again, this is >> experimental and not fully supported at this point. >> +Increased test coverage for soaplib and supported servers. >> >> Upcoming soaplib organization releases: >> >> Tres Seaver has built a WSRP (Web Services for Remote Portlets) >> library called wsrplib on top of soaplib. ?This library is being >> release shortly under the soaplib organization and can currently be >> found at https://github.com/soaplib/wsrplib . ?Many of the recent API >> additions to soaplib were driven by this effort. ?Once again, this >> work would not have been possible without the sponsorship of ZeOmega. >> >> >> We are interested in establishing a robust community process to >> encourage adoption and contribution. Please let us know if you have >> input on how we can get there; the goal is to provide a solid >> end-to-end choice for working with SOAP using Python. >> >> >> Additional thanks go out to everyone who has made suggestions, rants, >> and most importantly submitted any type of bugfix. >> _______________________________________________ >> Soap mailing list >> Soap at python.org >> http://mail.python.org/mailman/listinfo/soap > > > > -- > Cristian Salamea > @ovnicraft > From bradallen137 at gmail.com Fri Jan 21 00:41:05 2011 From: bradallen137 at gmail.com (Brad Allen) Date: Thu, 20 Jan 2011 17:41:05 -0600 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: On Thu, Jan 20, 2011 at 5:26 PM, Ovnicraft wrote: >> +The soaplib client has been re-written after having been dropped from >> recent releases. It follows the suds API but is based on lxml for >> better performance. WARNING: the soaplib client is not well-tested and >> future support is tentative dependent on community response. ? It's >> current location is in a seperate repo at >> https://github.com/soaplib/soaplib.client > > Believe in suds. IMHO more effort can applied in soaplib as server We agree, and don't have time to support the soaplib client, but didn't want to throw it away in case anyone else wanted to work on it. Burak introduced it along the way but is no longer available to support it. It wasn't passing tests in the soaplib package, so we split it out into a separate package (soaplib.client) where anyone is welcome to come along and become the new maintainer...or not. From ovnicraft at gmail.com Fri Jan 21 00:47:02 2011 From: ovnicraft at gmail.com (Ovnicraft) Date: Thu, 20 Jan 2011 18:47:02 -0500 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: On Thu, Jan 20, 2011 at 6:41 PM, Brad Allen wrote: > On Thu, Jan 20, 2011 at 5:26 PM, Ovnicraft wrote: > >> +The soaplib client has been re-written after having been dropped from > >> recent releases. It follows the suds API but is based on lxml for > >> better performance. WARNING: the soaplib client is not well-tested and > >> future support is tentative dependent on community response. It's > >> current location is in a seperate repo at > >> https://github.com/soaplib/soaplib.client > > > > Believe in suds. IMHO more effort can applied in soaplib as server > > We agree, and don't have time to support the soaplib client, but > didn't want to throw it away in case anyone else wanted to work on it. > Burak introduced it along the way but is no longer available to > support it. It wasn't passing tests in the soaplib package, so we > split it out into a separate package (soaplib.client) where anyone is > welcome to come along and become the new maintainer...or not. > split was a good choice Regards, -- Cristian Salamea @ovnicraft -------------- next part -------------- An HTML attachment was scrubbed... URL: From esiotrot at gmail.com Fri Jan 21 08:38:05 2011 From: esiotrot at gmail.com (Michael Wood) Date: Fri, 21 Jan 2011 09:38:05 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: Hi On 21 January 2011 00:53, Chris Austin wrote: > We are pleased to announce 2.1.0-beta1 of soaplib. This introduces > significant API changes since the 2.1.0-alpha released in Sept 2010. Great :) > This release also marks the transition to new maintainers (Brad Allen > and Chris Austin), and a new repository location indicated on the new > PyPI record (?https://github.com/soapapistas/soaplib). Ummm... can't we go 2 months without changing the location of the repository? :) What happened to github.com/soaplib/soaplib? Actually, I see the soapapistas link gives a 404 error (like the one mentioned by Ovnicraft for the Sphinx docs) so is https://github.com/soaplib/soaplib still the correct URL for the repository? > We are interested in establishing a robust community process to > encourage adoption and contribution. Please let us know if you have > input on how we can get there; the goal is to provide a solid > end-to-end choice for working with SOAP using Python. I've only been using soaplib for a couple of months, and it's great, but one thing that's a little confusing is the proliferation of unfinished branches. i.e 0.8 beta, 1.0 beta, 2.0 alpha, 2.1 beta. I realise this is probably just because of the history of the project, but it would be a lot less confusing if someone could just tag a 1.0 final release or something so that someone who wants stable and working code (even if it's not guaranteed to be bug free) knows what to use. It is my impression that everything other than current master has been abandoned. Is this the case? Or is it planned to release a final 1.0 version at some point? Anyway, the above doesn't affect me anymore. I'm using 1.0 and will probably stick with it for the moment, but new users might have a slightly easier time if it's clearer which branch they should be using. Thanks. -- Michael Wood From esiotrot at gmail.com Fri Jan 21 08:52:40 2011 From: esiotrot at gmail.com (Michael Wood) Date: Fri, 21 Jan 2011 09:52:40 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: On 21 January 2011 09:38, Michael Wood wrote: > Hi > > On 21 January 2011 00:53, Chris Austin wrote: >> We are pleased to announce 2.1.0-beta1 of soaplib. This introduces >> significant API changes since the 2.1.0-alpha released in Sept 2010. I see that the tag "2.0.0b1" was created in the repository. Was this supposed to be 2.1.0b1? Also, it's inconsistent with the other tags where "alpha", "beta" etc. are spelled out. -- Michael Wood From bradallen137 at gmail.com Fri Jan 21 15:29:41 2011 From: bradallen137 at gmail.com (Brad Allen) Date: Fri, 21 Jan 2011 08:29:41 -0600 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: On Fri, Jan 21, 2011 at 1:38 AM, Michael Wood wrote: > Ummm... ?can't we go 2 months without changing the location of the > repository? :) ?What happened to github.com/soaplib/soaplib? > > Actually, I see the soapapistas link gives a 404 error (like the one > mentioned by Ovnicraft for the Sphinx docs) so is > https://github.com/soaplib/soaplib still the correct URL for the > repository? Sorry, there was a mistake in the announcement. The correct URL for the docs is here: http://soaplib.github.com/soaplib/2_0/ The permanent home for source code is here: https://github.com/soaplib/soaplib > I've only been using soaplib for a couple of months, and it's great, > but one thing that's a little confusing is the proliferation of > unfinished branches. ?i.e 0.8 beta, 1.0 beta, 2.0 alpha, 2.1 beta. Good point; some cleanup is needed in the tags to make sure they reflect reality. There was no 2.1 release. > I realise this is probably just because of the history of the project, > but it would be a lot less confusing if someone could just tag a 1.0 > final release or something so that someone who wants stable and > working code (even if it's not guaranteed to be bug free) knows what > to use. That's a good suggestion; are there any naysayers? > It is my impression that everything other than current master has been > abandoned. ?Is this the case? ?Or is it planned to release a final 1.0 > version at some point? No changes are planned for those earlier releases, as far as I know. However, if anyone wishes to contribute to the earlier branches, we'll be responsive about merging pull requests, etc. We want to build a community process and get more people involved. > Anyway, the above doesn't affect me anymore. ?I'm using 1.0 and will > probably stick with it for the moment, but new users might have a > slightly easier time if it's clearer which branch they should be > using. Is 1.0 working for you in production? I haven't heard much feedback about that release. From esiotrot at gmail.com Fri Jan 21 15:56:38 2011 From: esiotrot at gmail.com (Michael Wood) Date: Fri, 21 Jan 2011 16:56:38 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: On 21 January 2011 16:29, Brad Allen wrote: > On Fri, Jan 21, 2011 at 1:38 AM, Michael Wood wrote: >> Ummm... ?can't we go 2 months without changing the location of the >> repository? :) ?What happened to github.com/soaplib/soaplib? >> >> Actually, I see the soapapistas link gives a 404 error (like the one >> mentioned by Ovnicraft for the Sphinx docs) so is >> https://github.com/soaplib/soaplib still the correct URL for the >> repository? > > Sorry, there was a mistake in the announcement. The correct URL for > the docs is here: > > ? ?http://soaplib.github.com/soaplib/2_0/ > > The permanent home for source code is here: > > ? ?https://github.com/soaplib/soaplib Thanks for the clarification. >> Anyway, the above doesn't affect me anymore. ?I'm using 1.0 and will >> probably stick with it for the moment, but new users might have a >> slightly easier time if it's clearer which branch they should be >> using. > > Is 1.0 working for you in production? I haven't heard much feedback > about that release. Yes, I'm not doing anything fancy with it. It is working well :) -- Michael Wood From burak.arslan at arskom.com.tr Sat Jan 22 12:24:45 2011 From: burak.arslan at arskom.com.tr (Burak Arslan) Date: Sat, 22 Jan 2011 13:24:45 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: <4D3ABE7D.2010200@arskom.com.tr> On 01/21/11 09:38, Michael Wood wrote: > Hi > > On 21 January 2011 00:53, Chris Austin wrote: >> We are pleased to announce 2.1.0-beta1 of soaplib. This introduces >> significant API changes since the 2.1.0-alpha released in Sept 2010. > Great :) > >> This release also marks the transition to new maintainers (Brad Allen >> and Chris Austin), and a new repository location indicated on the new >> PyPI record ( https://github.com/soapapistas/soaplib). > Ummm... can't we go 2 months without changing the location of the > repository? :) What happened to github.com/soaplib/soaplib? > > Actually, I see the soapapistas link gives a 404 error (like the one > mentioned by Ovnicraft for the Sphinx docs) so is > https://github.com/soaplib/soaplib still the correct URL for the > repository? > >> We are interested in establishing a robust community process to >> encourage adoption and contribution. Please let us know if you have >> input on how we can get there; the goal is to provide a solid >> end-to-end choice for working with SOAP using Python. > I've only been using soaplib for a couple of months, and it's great, > but one thing that's a little confusing is the proliferation of > unfinished branches. i.e 0.8 beta, 1.0 beta, 2.0 alpha, 2.1 beta. > > I realise this is probably just because of the history of the project, > but it would be a lot less confusing if someone could just tag a 1.0 > final release or something so that someone who wants stable and > working code (even if it's not guaranteed to be bug free) knows what > to use. > > https://github.com/arskom/rpclib/tree/soaplib-1.0.0 http://pypi.python.org/pypi/soaplib/1.0.0 https://github.com/arskom/rpclib/tree/soaplib-0.8.2 http://pypi.python.org/pypi/soaplib/0.8.2 http://mail.python.org/pipermail/soap/2010-November/000325.html best, burak From esiotrot at gmail.com Sun Jan 23 02:14:21 2011 From: esiotrot at gmail.com (Michael Wood) Date: Sun, 23 Jan 2011 03:14:21 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: <4D3ABE7D.2010200@arskom.com.tr> References: <4D3ABE7D.2010200@arskom.com.tr> Message-ID: On 22 January 2011 13:24, Burak Arslan wrote: > ?On 01/21/11 09:38, Michael Wood wrote: [...] >> I've only been using soaplib for a couple of months, and it's great, >> but one thing that's a little confusing is the proliferation of >> unfinished branches. ?i.e 0.8 beta, 1.0 beta, 2.0 alpha, 2.1 beta. >> >> I realise this is probably just because of the history of the project, >> but it would be a lot less confusing if someone could just tag a 1.0 >> final release or something so that someone who wants stable and >> working code (even if it's not guaranteed to be bug free) knows what >> to use. > > https://github.com/arskom/rpclib/tree/soaplib-1.0.0 > http://pypi.python.org/pypi/soaplib/1.0.0 > > https://github.com/arskom/rpclib/tree/soaplib-0.8.2 > http://pypi.python.org/pypi/soaplib/0.8.2 > > http://mail.python.org/pipermail/soap/2010-November/000325.html Oh, thanks for the info. I see they were released and announced just after I started using soaplib, but before I joined this mailing list, so I didn't know about them. Also, the above tags do not exist in the current soaplib/soaplib repository and did not exist in the arskom/soaplib when I last pulled from it before it disappeared. I see that there's no difference between 1.0.0-beta8 and 1.0.0 release except for the version, so perhaps that should be done in the soaplib/soaplib repository too (e.g. by cherry-picking 2801978f51390772de0ac7ff05f0854dddfdd076 from arskom/rpclib). The situation for 0.8 is the same (see ee25b4c25d23f1f54d86f30103762ae9c7f2e7aa in arskom/rpclib). Then if https://github.com/soaplib/soaplib/downloads is updated (if it doesn't happen automatically) I think that would put this issue to bed :) -- Michael Wood From esiotrot at gmail.com Sun Jan 23 02:30:50 2011 From: esiotrot at gmail.com (Michael Wood) Date: Sun, 23 Jan 2011 03:30:50 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: <4D3ABE7D.2010200@arskom.com.tr> Message-ID: On 23 January 2011 03:14, Michael Wood wrote: > On 22 January 2011 13:24, Burak Arslan wrote: >> ?On 01/21/11 09:38, Michael Wood wrote: > [...] >>> I've only been using soaplib for a couple of months, and it's great, >>> but one thing that's a little confusing is the proliferation of >>> unfinished branches. ?i.e 0.8 beta, 1.0 beta, 2.0 alpha, 2.1 beta. >>> >>> I realise this is probably just because of the history of the project, >>> but it would be a lot less confusing if someone could just tag a 1.0 >>> final release or something so that someone who wants stable and >>> working code (even if it's not guaranteed to be bug free) knows what >>> to use. >> >> https://github.com/arskom/rpclib/tree/soaplib-1.0.0 >> http://pypi.python.org/pypi/soaplib/1.0.0 >> >> https://github.com/arskom/rpclib/tree/soaplib-0.8.2 >> http://pypi.python.org/pypi/soaplib/0.8.2 >> >> http://mail.python.org/pipermail/soap/2010-November/000325.html > > Oh, thanks for the info. > > I see they were released and announced just after I started using > soaplib, but before I joined this mailing list, so I didn't know about > them. ?Also, the above tags do not exist in the current > soaplib/soaplib repository and did not exist in the arskom/soaplib > when I last pulled from it before it disappeared. > > I see that there's no difference between 1.0.0-beta8 and 1.0.0 release > except for the version, so perhaps that should be done in the > soaplib/soaplib repository too (e.g. by cherry-picking > 2801978f51390772de0ac7ff05f0854dddfdd076 from arskom/rpclib). > > The situation for 0.8 is the same (see > ee25b4c25d23f1f54d86f30103762ae9c7f2e7aa in arskom/rpclib). Sorry, it's more complicated for 0.8. soaplib-0.8.2 is basically 2f4dae57589fd20be6d50137f833486eab9284eb with the "-beta2" removed from tag_build, but the 0_8 branch in soaplib/soaplib has some extra commits that are not in arskom/rpclib. So I'm not sure what's best there. Maybe a 0.8.2.1 or 0.8.3 could be released as well as tagging 0.8.2? -- Michael Wood From dieter at handshake.de Sun Jan 23 08:31:28 2011 From: dieter at handshake.de (Dieter Maurer) Date: Sun, 23 Jan 2011 08:31:28 +0100 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: References: Message-ID: <19771.55632.250649.621728@gargle.gargle.HOWL> Brad Allen wrote at 2011-1-21 08:29 -0600: > ... >> I realise this is probably just because of the history of the project, >> but it would be a lot less confusing if someone could just tag a 1.0 >> final release or something so that someone who wants stable and >> working code (even if it's not guaranteed to be bug free) knows what >> to use. > >That's a good suggestion; are there any naysayers? Nothing is guaranted to be bug free. But known problems should be documented. And if some of these were grave, no final release should be published. Not publishing a final release indicates "this version has been abondoned and probably should not be used". Thus, we should publish a final release when the indication is not true. -- Dieter From esiotrot at gmail.com Sun Jan 23 17:31:09 2011 From: esiotrot at gmail.com (Michael Wood) Date: Sun, 23 Jan 2011 18:31:09 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: <19771.55632.250649.621728@gargle.gargle.HOWL> References: <19771.55632.250649.621728@gargle.gargle.HOWL> Message-ID: On 23 January 2011 09:31, Dieter Maurer wrote: > Brad Allen wrote at 2011-1-21 08:29 -0600: >> ... >>> I realise this is probably just because of the history of the project, >>> but it would be a lot less confusing if someone could just tag a 1.0 >>> final release or something so that someone who wants stable and >>> working code (even if it's not guaranteed to be bug free) knows what >>> to use. >> >>That's a good suggestion; are there any naysayers? > > Nothing is guaranted to be bug free. But known problems should > be documented. And if some of these were grave, no final release > should be published. Except that, as mentioned by Burak, 0.8.2 and 1.0.0 were actually released. Just from the arskom/rpclib repository. So it's too late not to publish them now. > Not publishing a final release indicates "this version has > been abondoned and probably should not be used". > Thus, we should publish a final release when the indication is not true. -- Michael Wood From chris at sydneysys.com Mon Jan 24 18:13:34 2011 From: chris at sydneysys.com (Chris Austin) Date: Mon, 24 Jan 2011 11:13:34 -0600 (CST) Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: Message-ID: <17772635.2.1295889210567.JavaMail.chris@dAlembertian> The 0.8.2 and 1.0.0 downloads and tags now exist at soaplib/soaplib. Go ahead and take a look and see if this meets your needs. Cheers ----- Original Message ----- From: "Michael Wood" To: "Dieter Maurer" Cc: soap at python.org Sent: Sunday, January 23, 2011 10:31:09 AM Subject: Re: [Soap-Python] Soaplib beat1 released into the wild On 23 January 2011 09:31, Dieter Maurer wrote: > Brad Allen wrote at 2011-1-21 08:29 -0600: >> ... >>> I realise this is probably just because of the history of the project, >>> but it would be a lot less confusing if someone could just tag a 1.0 >>> final release or something so that someone who wants stable and >>> working code (even if it's not guaranteed to be bug free) knows what >>> to use. >> >>That's a good suggestion; are there any naysayers? > > Nothing is guaranted to be bug free. But known problems should > be documented. And if some of these were grave, no final release > should be published. Except that, as mentioned by Burak, 0.8.2 and 1.0.0 were actually released. Just from the arskom/rpclib repository. So it's too late not to publish them now. > Not publishing a final release indicates "this version has > been abondoned and probably should not be used". > Thus, we should publish a final release when the indication is not true. -- Michael Wood _______________________________________________ Soap mailing list Soap at python.org http://mail.python.org/mailman/listinfo/soap From rprikhodchenko at gmail.com Sun Jan 23 12:04:50 2011 From: rprikhodchenko at gmail.com (Roman Prykhodchenko) Date: Sun, 23 Jan 2011 13:04:50 +0200 Subject: [Soap-Python] rpclib/soaplib In-Reply-To: <4D3ABAC7.6040304@arskom.com.tr> References: <4717851F-8653-45FB-84BC-E8D231D53290@gmail.com> <4D3ABAC7.6040304@arskom.com.tr> Message-ID: <6B6AE040-1170-4E4F-9C7A-9AE3824F7936@gmail.com> Hello guys, As I founded it, there are no fine-wroking python library for creating SOAP services. I have tested some of them and soaplib/rpclib seemed to be the best one. However Burak told me that this library i not ready to be used in production yet. I think I can help you with this issue. I am a lecturer at Kharkiv National University of Radio Electronics. My students have to make their projects during this half-year. I teach third year students programming and I think it would be a great idea if they had an opportunity to work on real open-source projects rather than creating their own equation solvers or other useless apps. Here is my vision of such collaboration: - I ask students who would like to work on this project and we choose one - You select the supervisor for the student. The supervisor will be the student's "boss" and will give him tasks and help in solving complex problems. - The project should take student two-three months of time and you can decide which part(s) of the soaplib/rpclib can be developed by student during this term. - The student discusses tasks and agrees them with me. - When the tasks are agreed the student begins working on your library and writing his Project report. - During the term I will coordinate the student and will solve organization problems. - When the term is finished the student should complete all tasks, agreed on the beginning of the term and also the student should finish his Project report. - The student can continue working on soaplib/rpclib after the science project is finished, if he likes it. There some big advantages in such collaboration for all participants: - You get a contributor that is interested in working on your project. - The student gets the experience in working on a project that is useful for a real world. - You can get the stable and ready for production library with help of the student. - If soaplib/rpclib is interested to student he will continue working on it after the science project is finished. Please consider my proposal and tell me what do you think about such collaboration. Sincerely, Roman Prykhodchenko Kharkiv National University of Radio Electronics On Jan 22, 2011, at 1:08 PM, Burak Arslan wrote: > On 01/16/11 15:34, Roman Prykhodchenko wrote: >> >> Hello Burak, >> >> As I can see you are one of the most active developers of rpclib/soaplib. I use this library for one of my projects that has to be very robust and stable. >> There are several versions of rpclib/soaplib on the github. There are a lot of mess in the documentation so I cannot understand what version is the latest stable version. >> There are some incompatibilities between different versions so I need to chose the most stable and well documented one. Can you help me to make a choice? >> >> Sincerely, >> Roman Prykhodchenko > > > hi roman, > > it's correct that i've done most of the work on soaplib/rpclib, but there's still a lot to be done. don't base your work on anything you may find on github.com/arskom or github.com/plq, as i'm away (i'm in front of a computer once a week for a few hours) and not able to support anything. > > please divert any further correspondance to soap at python.org where the my successors as the maintainers of soaplib lurk. > > i wish you best of luck with your endeavors. > burak > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at sydneysys.com Mon Jan 24 20:57:28 2011 From: chris at sydneysys.com (Chris Austin) Date: Mon, 24 Jan 2011 13:57:28 -0600 Subject: [Soap-Python] rpclib/soaplib In-Reply-To: <6B6AE040-1170-4E4F-9C7A-9AE3824F7936@gmail.com> References: <4717851F-8653-45FB-84BC-E8D231D53290@gmail.com> <4D3ABAC7.6040304@arskom.com.tr> <6B6AE040-1170-4E4F-9C7A-9AE3824F7936@gmail.com> Message-ID: Hi Roman, First off, your offer is most gracious and I'd love to take you up on it. Second, I'd like to give you a little bit of background of where we are hoping to go forward with soaplib. We've recently released a new beta of soaplib 2.0. So, we are looking to find and quash as many bugs as we can without altering the API further at this point. Realistically, this means improving the following: +test coverage +test cases + interoperability testing with java and .net clients +improved doc strings for modules and the public API +improving the project documentation +fixing bugs once bug reports for the 2.0 beta. +and more maintenance items I am sure I've forgotten Once we release a solid 2.0 we can start planning non-breaking changes for 2.x.x and beyond. I realize this might sound a bit drab but I want to be honest about what your student would be expecting to get done. If you and your students are still interested, feel free to contact me and I can start moving forward with some planning. Cheers On Sun, Jan 23, 2011 at 5:04 AM, Roman Prykhodchenko wrote: > Hello guys, > > As I founded it, there are no fine-wroking python library for creating SOAP > services. I have tested some of them and soaplib/rpclib seemed to be the > best one. > However Burak told me that this library i not ready to be used in production > yet. I think I can help you with this issue. > I am a lecturer at Kharkiv National University of Radio Electronics. My > students have to make their projects during this half-year. I teach third > year students programming and I think it would be a great idea if they had > an opportunity to work on real open-source projects rather than creating > their own equation solvers or other useless apps. Here is my vision of such > collaboration: > - I ask students who would like to work on this project and we choose one > - You select the supervisor for the student. The supervisor will be the > student's "boss" and will give him tasks and help in solving complex > problems. > - The project should take student two-three months of time and you can > decide which part(s) of the soaplib/rpclib can be developed by student > during this term. > - The student discusses tasks and agrees them with me. > - When the tasks are agreed the student begins working on your library and > writing his Project report. > - During the term I will coordinate the student and will solve organization > problems. > - When the term is finished the student should complete all tasks, agreed on > the beginning of the term and also the student should finish his Project > report. > - The student can continue working on soaplib/rpclib after the science > project is finished, if he likes it. > There some big advantages in such collaboration for all participants: > - You get a contributor that is interested in working on your project. > - The student gets the experience in working on a project that is useful for > a real world. > - You can get the stable and ready for production library with help of the > student. > - If soaplib/rpclib is interested to student he will continue working on it > after the science project is finished. > Please consider my proposal and tell me what do you think about such > collaboration. > > Sincerely, > Roman Prykhodchenko > Kharkiv National University of Radio Electronics > > > > On Jan 22, 2011, at 1:08 PM, Burak Arslan wrote: > > On 01/16/11 15:34, Roman Prykhodchenko wrote: > > Hello?Burak, > As I can see you are one of the most active developers of?rpclib/soaplib. I > use this library for one of my projects that has to be very robust and > stable. > There are several versions of rpclib/soaplib on the github. There are a lot > of mess in the documentation so I cannot understand what version is the > latest stable version. > There are some incompatibilities between different versions so I need to > chose the most stable and well documented one. Can you help me to make a > choice? > Sincerely, > Roman Prykhodchenko > > hi roman, > > it's correct that i've done most of the work on soaplib/rpclib, but there's > still a lot to be done. don't base your work on anything you may find on > github.com/arskom or github.com/plq, as i'm away (i'm in front of a computer > once a week for a few hours) and not able to support anything. > > please divert any further correspondance to soap at python.org where the my > successors as the maintainers of soaplib lurk. > > i wish you best of luck with your endeavors. > burak > > > > > _______________________________________________ > Soap mailing list > Soap at python.org > http://mail.python.org/mailman/listinfo/soap > > From esiotrot at gmail.com Mon Jan 24 22:20:23 2011 From: esiotrot at gmail.com (Michael Wood) Date: Mon, 24 Jan 2011 23:20:23 +0200 Subject: [Soap-Python] Soaplib beat1 released into the wild In-Reply-To: <17772635.2.1295889210567.JavaMail.chris@dAlembertian> References: <17772635.2.1295889210567.JavaMail.chris@dAlembertian> Message-ID: On 24 January 2011 19:13, Chris Austin wrote: > > The 0.8.2 and 1.0.0 downloads and tags now exist at soaplib/soaplib. ?Go ahead and take a look and see if this meets your needs. Looks fine to me :) Thanks. -- Michael Wood From itssami.gb4u at gmail.com Thu Jan 27 07:51:43 2011 From: itssami.gb4u at gmail.com (sami nathan) Date: Thu, 27 Jan 2011 12:21:43 +0530 Subject: [Soap-Python] parsing SOAP request Message-ID: Hi i am working in django web service i am getting SOAP(POST) request from client now i am trying to parse the request xml and sending the response my soap request is 12345343661t1p1p2DICT test']}> response now i want send response as change is denoted in colors '12345343661t1p1p2TEXT HERE ']}> -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at sydneysys.com Thu Jan 27 16:24:49 2011 From: chris at sydneysys.com (Chris Austin) Date: Thu, 27 Jan 2011 09:24:49 -0600 (CST) Subject: [Soap-Python] parsing SOAP request In-Reply-To: Message-ID: <15997082.3.1296141885544.JavaMail.chris@dAlembertian> Hi Sami, Your colors aren't showing up in my email client so I'll do my best to punt and guess at what you are trying to do. If you are using soaplib to serve this WS I'd probably do something like the following. class YourDataType(ClassModel): unique_id = Integer application_id = Integer transaction_id = Integer placeholder_1 = String placeholder_2 = String message = String class YourService(DefinitionBase): @soap(YourDataType, _returns=YourDataType) def processs_samis_request(self, your_data_type): ... # doing domiain logic..... ... return your_data_type_instance Where the instance 'your_data_type_instance' is a modified instance of 'YourDataType' that you've updated per your needs. Hope this helps. ----- Original Message ----- From: "sami nathan" To: soap at python.org Sent: Thursday, January 27, 2011 12:51:43 AM Subject: [Soap-Python] parsing SOAP request Hi i am working in django web service i am getting SOAP(POST) request from client now i am trying to parse the request xml and sending the response my soap request is 12345343661t1p1p2DICT test']}> response now i want send response as change is denoted in colors '12345343661t1p1p2 TEXT HERE ']}> _______________________________________________ Soap mailing list Soap at python.org http://mail.python.org/mailman/listinfo/soap