I am recently heavily engaged in Web Service applications, the services themselves were written in Java, which is I believe the best choice at moment, considering the language as well as the infrastructure that backs it up.
But i also need some testing programs, and I want the testing cases be written in something other than Java (so to show a bit interoperatability), and I want something handy, so it comes down to Perl and Ruby. Perl and SOAP::Lite was my first choice, as i am more familiar with Perl.
However SOAP::Lite broke into pieces right the way. It turned out SOAP::Lite is poor with namespace and WSDL. At first, I thought that I was doing something wrong, but the package was right. To sperate my own mistake from bugs inside SOAP::Lite. I tried wsdl stub maker. But the generated stub didn't work, and complained about schema (which is the same issue when I coded through SOAP::Lite->service()).
I was forced to use Java to test Java, I tried two different Java implementations, and both worked. So I was quit sure the problem is with Perl, not the server side implementation. But there was still some doubt in my mind, what if the Java implementation both used the same foundation classes a the server side (that could be!).
This morning, I was in a good mood, so I thought, why not try Ruby. I never used Ruby with WSDL (or SOAP) before. But I managed to quickly find a piece of example online (thanks google). After had fun with it, and the online ruby documentation, I quickly made everything work.
Now I no lnger have any doubt that the SOAP::Lite is broken. Perl SOAP support is kinda stopped at the basics. 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.
In reply to SOAP and Perl by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |