in reply to SOAP and Perl

You do realize, of course, that SOAP::Lite is, as its name implies, "lite"? Trouble with SOAP::Lite could very well be that you need to do something with your SOAP/WSDL service that SOAP::Lite doesn't handle well.

But, then, all you tried was SOAP::Lite before saying "Perl SOAP support is kinda stopped at the basics" -- seems like your skills and attitude are somewhat in question here. Did you maybe consider using the full SOAP modules instead of trying to "get by" with SOAP::Lite?

Sorry if that seems a little harsh, but when you say things like "I know that nobody here want to hear the downside of Perl, but as you can see, I am telling the story as it is", you're going to get that reaction for two reasons:

  1. Lots of people hear are willing to discuss the weaknesses and shortcomings of Perl itself and of various modules on the CPAN, and
  2. Problems with 3rd-party modules, like the majority found on the CPAN, are not problems with Perl; your statement belies a lack of any serious history with Perl or the community.

Further, you haven't given us any reason to believe that the problem isn't you. For example, did you ask for help? What did you do that didn't work? What's your definition of "didn't work"? Did you consider that the problem might not be SOAP::Lite or Perl, per se, but confusing documentation or some other issue?

Simply ranting about an experience you had where a module didn't work for you -- without any of the details, any history, etc. -- and then condemning the entire Perl language (on a Perl forum) based on that smells like a troll. If it wasn't supposed to be a troll, ok, but I have to wonder what's productive about complaining when you don't provide any details that would let anyone help resolve that complaint...

<radiant.matrix>
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet