With out starting a lot of flaming and religious wars, I think the whole idea of using WSDL to dynamically build message handling is over-blown. Sure, the message interface might change but will my program be able to handle the changes without involving code changes? Maybe, for simple things but for those who cares. For complex changes it is a whole different story.
I am happy to have something handle all the mundane things even if it statically built.
Amit Upadhyay wrote:
On 2/15/06, *David E. Konerding* <email@example.com mailto:firstname.lastname@example.org> wrote:
If you check out the serialize-dom-scheme branch, you get a really nice WSDL code generator for Python (much, much better than SOAPpy or normal ZSI). Then, go get pyGridWare. It adds a Twisted service container that can house ZSI-based web services.
WSDL code generation completely defies the purpose of having WSDL in the first place, refer: http://webservices.xml.com/pub/a/ws/2003/07/22/wsdlfirst.html http://webservices.xml.com/pub/a/ws/2003/07/22/wsdlfirst.html
<Rant> Its a shame that no python soap implementation supports WSDL first approach, while PHP being a weakly typed language does.
More at http://nerdierthanthou.nfshost.com/2005/09/soaped-django.html
-- Amit Upadhyay Blog: http://www.rootshell.be/~upadhyay http://www.rootshell.be/%7Eupadhyay
Twisted-web mailing list Twistedemail@example.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web