In general found SOAP::Lite does a good job, including WSDL support - it's been possible to do everything I needed to with it, such as hooking up to a fairly complex webmethods Java service. I haven't found any significant shortcomings in terms of what it supports but if you have anything unusual about the service you are accessing, you have to get familiar with the source - learning curve. Oh - and you need to have a pretty good understanding of SOAP and WSDL (e.g. you can interpret the raw XML).
The only gripe I have is it hides LWP too much - it's hard to get decent HTTP debugging out of it.
Think the problem isn't so much SOAP::Lite but rather that SOAP itself is a joke - way too complex - designed by committee, supporting use cases that will only ever exist for 0.0001% of it's users. And it's a protocol on top of a protocol (HTTP normally) - that already makes for a debugging / testing disaster.
In practice, writing a new library to support everything SOAP + WSDL does is going to be a ton of work.
It's summed up nicely here:
(...) enterprise developers working for government agencies and businesses who see all the success that Web companies are having with simple technologies like RSS and RESTful web services while they have difficulty implementing SOAs in their enterprises for a smaller audience than these web sites. The lesson here is that all this complexity being pushed by so-called enterprise architects, software vendors and big 5 consulting companies is bullshit.
In reply to Re: start over with SOAP in Perl?
by harryf
in thread start over with SOAP in Perl?
by McMahon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |