I did look at soaplib. The API for writing clients is really bad, and on top of that I couldn't get it to talk to the service in question. The API for writing servers looked fine I guess, but I'm not in a position to where I'd ever have or want to create a SOAP service.
elementsoap worked great, eventually, but it doesn't really do anything for you beyond shorthand for creating the request documents.... which is probably why it worked. -bob On 2/19/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > I've been using the new soaplib library in a couple of projects, and > while I think SOAP sucks, I know that soaplib makes it "suck less." > > With that said, I'd doubt that soaplib would help with either of your > problems, as they seem to have been the result of seriously broken > soap libraries. Of course the complexity, ambiguity, and handwaving > of the SOAP spec in various areas pretty much makes writing broken > implementations unavoidable. > > My point is just that sometimes you have to deal with SOAP, and it > will be a good thing for Python if we have tools that make SOAP less > frustrating and painful. > > --Mark Ramm > > > SOAP is a total nightmare. It's the most complicated and least > > efficient way to do anything. > > > > 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 eventually managed to get it to work using elementsoap, after > > failing miserably with ZSI and SOAPpy. I had to hack in dumping of the > > XML back and forth to figure out what was actually happening. > > > > This is actually the second time I've used SOAP... the first time was > > similarly screwed up -- the service I was talking to was written in C > > and didn't actually use an XML parser (nor was it a correct HTTP > > implementation). Ugh. > > > > XML-RPC, url encoded variables, JSON, and anything else REST-ish have > > always worked out pretty well for me though. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
