From bradallen137 at gmail.com  Wed Feb  2 20:54:15 2011
From: bradallen137 at gmail.com (Brad Allen)
Date: Wed, 2 Feb 2011 13:54:15 -0600
Subject: [Soap-Python] Soaplib beat1 released into the wild
In-Reply-To: <AANLkTinabDb7y83Rg7nyVFMXgQ=k6j+ksEtfX2f_X5Cp@mail.gmail.com>
References: <AANLkTimteowGBHcEPZ5CrZuPkF3TsuNhibkujOf7xyK+@mail.gmail.com>
	<17772635.2.1295889210567.JavaMail.chris@dAlembertian>
	<AANLkTinabDb7y83Rg7nyVFMXgQ=k6j+ksEtfX2f_X5Cp@mail.gmail.com>
Message-ID: <AANLkTik6j3P71+K7kx_ppW2g3m8r2nFzribq+H2DOXW-@mail.gmail.com>

We haven't gotten much feedback about soaplib 2.0 beta; has anyone
reviewed the Sphinx docs, done any testing, etc?

Btw, in case anyone notices Zope missing, that is going into a
separate package with ZCA support added, but has not yet been pushed
to GitHub. It should appear sometime soon.

From bradallen137 at gmail.com  Wed Feb  2 20:56:09 2011
From: bradallen137 at gmail.com (Brad Allen)
Date: Wed, 2 Feb 2011 13:56:09 -0600
Subject: [Soap-Python] SOAP at US PyCon 2011
Message-ID: <AANLkTik2+XLNGcO9c_OeyGwpa8DUjgtFr9ZTAzaYO1in@mail.gmail.com>

Does anyone on the SOAP list want to meet up at US PyCon 2011 for a
SOAP BOF or open space? I'll also be around for the sprint days but am
undecided about which project to work on.

From esiotrot at gmail.com  Fri Feb  4 09:13:08 2011
From: esiotrot at gmail.com (Michael Wood)
Date: Fri, 4 Feb 2011 10:13:08 +0200
Subject: [Soap-Python] Soaplib beat1 released into the wild
In-Reply-To: <AANLkTik6j3P71+K7kx_ppW2g3m8r2nFzribq+H2DOXW-@mail.gmail.com>
References: <AANLkTimteowGBHcEPZ5CrZuPkF3TsuNhibkujOf7xyK+@mail.gmail.com>
	<17772635.2.1295889210567.JavaMail.chris@dAlembertian>
	<AANLkTinabDb7y83Rg7nyVFMXgQ=k6j+ksEtfX2f_X5Cp@mail.gmail.com>
	<AANLkTik6j3P71+K7kx_ppW2g3m8r2nFzribq+H2DOXW-@mail.gmail.com>
Message-ID: <AANLkTim4EfZF24NjmHurBLRsFYoFAHzh350jUqbAF+3-@mail.gmail.com>

On 2 February 2011 21:54, Brad Allen <bradallen137 at gmail.com> wrote:
> We haven't gotten much feedback about soaplib 2.0 beta; has anyone
> reviewed the Sphinx docs, done any testing, etc?

A week or so ago I gave 2.0.0b1 a try and it seemed like the changes
to get it to work would be quite small.  Mostly @rpc -> @soap and
[Ss]erializer -> [Mm]odel IIRC.

One thing I was not able to figure out in the short time I spent on
it, though, was how to get it to work with modwsgi.  It seems the way
this is done has changed with 2.0.

Basically, what I'm doing at the moment (with 1.0) is I have a file
(e.g. MyService.wsgi) that contains something like this:

========================
import MyService
from soaplib.wsgi import Application

application = Application([MyService.MyService], 'myns')
========================

When I try that with 2.0.0b1, though (after fixing up the
"Application" import IIRC), it seems that modwsgi tries to call
application, but there's no __call__() method.  I only spent a few
minutes looking at it and was not able to figure out what I was
supposed to do to make it work.  I plan to come back to it at some
point, but don't have the time right now.

Thanks :)

-- 
Michael Wood <esiotrot at gmail.com>

From chris at sydneysys.com  Tue Feb  8 17:52:49 2011
From: chris at sydneysys.com (Chris Austin)
Date: Tue, 8 Feb 2011 10:52:49 -0600 (CST)
Subject: [Soap-Python] Soaplib beat1 released into the wild
In-Reply-To: <AANLkTim4EfZF24NjmHurBLRsFYoFAHzh350jUqbAF+3-@mail.gmail.com>
Message-ID: <8093198.6.1297183964994.JavaMail.chris@dAlembertian>

Hi Michael,

Sorry I am late to getting to this; I've been a bit distracted from soaplib for a few days.

For some reason I never thought to put a mod_wsgi specific example in the docs.  In hindsight it seems completely like a no-brainier that it is a pretty common use case.  I'll try to update the docs later this week or early next week.


Now, soaplibs wsgi support should work just fine with mod_wsgi.  The difference that you've encountered here is because sometime after 1.0 it was discussed and decided that it would be nice not to tie soaplib directly to mod_wsgi.  The Application object was modified and the wsgi support was moved into a soaplib.core.server.wsgi.

To use this with a wsgi server it requires an extra import and extra line of code.

import MyService
import soaplib
from soaplib.core.server import wsgi

soap_app = soaplib.core.Application([MyService], "MyTns")
wsgi_app = wsgi.Application(soap_application)

Inside the wsgi_app, __call__() has been implemented.

Also, the hello world example in the project docs is a bit "prettier" and has a few a bit more explination.

Hope this helps. 




----- Original Message -----
From: "Michael Wood" <esiotrot at gmail.com>
To: "Brad Allen" <bradallen137 at gmail.com>
Cc: soap at python.org
Sent: Friday, February 4, 2011 2:13:08 AM
Subject: Re: [Soap-Python] Soaplib beat1 released into the wild

On 2 February 2011 21:54, Brad Allen <bradallen137 at gmail.com> wrote:
> We haven't gotten much feedback about soaplib 2.0 beta; has anyone
> reviewed the Sphinx docs, done any testing, etc?

A week or so ago I gave 2.0.0b1 a try and it seemed like the changes
to get it to work would be quite small.  Mostly @rpc -> @soap and
[Ss]erializer -> [Mm]odel IIRC.

One thing I was not able to figure out in the short time I spent on
it, though, was how to get it to work with modwsgi.  It seems the way
this is done has changed with 2.0.

Basically, what I'm doing at the moment (with 1.0) is I have a file
(e.g. MyService.wsgi) that contains something like this:

========================
import MyService
from soaplib.wsgi import Application

application = Application([MyService.MyService], 'myns')
========================

When I try that with 2.0.0b1, though (after fixing up the
"Application" import IIRC), it seems that modwsgi tries to call
application, but there's no __call__() method.  I only spent a few
minutes looking at it and was not able to figure out what I was
supposed to do to make it work.  I plan to come back to it at some
point, but don't have the time right now.

Thanks :)

-- 
Michael Wood <esiotrot at gmail.com>
_______________________________________________
Soap mailing list
Soap at python.org
http://mail.python.org/mailman/listinfo/soap

From esiotrot at gmail.com  Thu Feb 17 08:53:20 2011
From: esiotrot at gmail.com (Michael Wood)
Date: Thu, 17 Feb 2011 09:53:20 +0200
Subject: [Soap-Python] Soaplib beat1 released into the wild
In-Reply-To: <8093198.6.1297183964994.JavaMail.chris@dAlembertian>
References: <AANLkTim4EfZF24NjmHurBLRsFYoFAHzh350jUqbAF+3-@mail.gmail.com>
	<8093198.6.1297183964994.JavaMail.chris@dAlembertian>
Message-ID: <AANLkTin0Gi3XKwo=e30Y0-GROkTzD0fMgF1HZFajy9aq@mail.gmail.com>

Hi Chris

On 8 February 2011 18:52, Chris Austin <chris at sydneysys.com> wrote:
> Hi Michael,
>
> Sorry I am late to getting to this; I've been a bit distracted from soaplib for a few days.

That's fine.  I'm sorry I haven't responded before now.  I have not
had a chance to try out your suggestions yet.  I will try again at
some point and report back, but I've been too busy with other things.

> For some reason I never thought to put a mod_wsgi specific example in the docs. ?In hindsight it seems completely like a no-brainier that it is a pretty common use case. ?I'll try to update the docs later this week or early next week.
>
> Now, soaplibs wsgi support should work just fine with mod_wsgi. ?The difference that you've encountered here is because sometime after 1.0 it was discussed and decided that it would be nice not to tie soaplib directly to mod_wsgi. ?The Application object was modified and the wsgi support was moved into a soaplib.core.server.wsgi.
>
> To use this with a wsgi server it requires an extra import and extra line of code.
>
> import MyService
> import soaplib
> from soaplib.core.server import wsgi
>
> soap_app = soaplib.core.Application([MyService], "MyTns")
> wsgi_app = wsgi.Application(soap_application)
>
> Inside the wsgi_app, __call__() has been implemented.

Ah, OK thanks.

> Also, the hello world example in the project docs is a bit "prettier" and has a few a bit more explination.

Thanks.  I'll have another look.

> Hope this helps.

Yes, I'm sure that will get me going when I have a chance to look at it again :)

Thanks again.

-- 
Michael Wood <esiotrot at gmail.com>

From mliu at biigroup.com  Thu Feb 24 11:24:46 2011
From: mliu at biigroup.com (Liu Ming)
Date: Thu, 24 Feb 2011 18:24:46 +0800
Subject: [Soap-Python] Help for complex type definition
Message-ID: <AANLkTik93SAFRbERsq2xShjJES_kmQ4oh6ie1tnn8avE@mail.gmail.com>

Hello everyone,

I try to define a type according to the wsdl following:

<s:complexType name="pointSet">
<s:sequence>
<s:element maxOccurs="unbounded" minOccurs="0" name="pointSet"
type="s0:pointSet"/>
<s:element maxOccurs="unbounded" minOccurs="0" name="point"
type="s0:point"/>
</s:sequence>
<s:attribute name="id" type="s:anyURI" use="required"/>
</s:complexType>

I write:

class PointSet(ClassModel):
__namespace__="http://gutp.jp/fiap/2009/11/"
__type_name__="pointSet"
pointSet = Array(PointSet)
point = Array(Point)

But error occurs:

NameError: name 'PointSet' is not defined

I think it is because PointSet has not finished DEFINITION, so you can't use
it. Is it right? How can I fix it?

Thank you very much

Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/soap/attachments/20110224/eca4d9ee/attachment.html>