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" <[email protected]> To: "Brad Allen" <[email protected]> Cc: [email protected] 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 <[email protected]> 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 <[email protected]> _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
