On 2/19/07, Bob Ippolito <[EMAIL PROTECTED]> wrote: > I think I wasted about 10 hours over the past few days trying to > figure out how to put together a SOAP client that would talk to a > poorly implemented SOAP service (written in PHP with NuSoap). Neither > the documentation or the WSDL file were correct and they didn't > provide example code in any language!
I have been there. Got it working eventually with ZSI. > XML-RPC, url encoded variables, JSON, and anything else REST-ish have > always worked out pretty well for me though. Same here. Mark is right in that you sometimes have to deal with it though and since MS-oriented programmers already have the gui wizards and whatnot to work with soap, I can make their life a little bit easier by providing a soap API, as long as I don't have to worry about the soap aspect myself. Hopefully soaplib does just that. What I like in TGWebServices is that they allow me to write a single api and expose it both via json-based calls and soap. Lately I wrote an api part to an existing mod_python app. I mark a module and automatically export all functions (except those starting with _ and otherwise marked with decorators). Since Python makes it easy to inspect the functions and their arguments, default values etc. it was easy to write a small handler that when called, returns a JavaScript api that proxies the calls over to loadJSONDoc for me. Can't post the code right since I'm at home, but if anyone's interested I can paste it somewhere (it's not in any way related to TurboGears though). Having automagic generation of the WSDL in the same way will be nice. Arnar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
