in reply to Re: WebService client with SOAP::Lite and ComplexType
in thread WebService client with SOAP::Lite and ComplexType
It would be more accurate to say:
Perl is a great language, but avoid it when it comes to web service interaction in other languages.
ie, it's fine to use SOAP::Lite -> SOAP::Lite, or even SOAP::Lite -> SOAP, but don't try mixing in gsoap, or any of the other SOAP toolkits w/out a whole bunch of headaches.
The problem? It's not Perl -- it's almost all SOAP -- it's like the early days of CSS -- the specifications came out, lots of people wrote to how they understood the specifications, and lo and behold, everyone came up with different interpretations, thus their toolkits weren't compatable. When you start mixing in different encoding types, languages that don't support certain data types, or mixing loose and strict typed toolkits, you're going to have problems.
Update: okay, before someone complains that the whole point of webservices is that it's intended to be language neutral, and so you're supposed to talk to other toolkits, yes, that's true. However, I've also run into other interaction problems in SOAP that didn't involve Perl, so it's not just a Perl thing -- it's bad implementations across the board. (I'm currently writing bad SOAP implementations in IDL, myself)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: WebService client with SOAP::Lite and ComplexType
by exussum0 (Vicar) on Jul 05, 2006 at 12:59 UTC | |
|
Re^3: WebService client with SOAP::Lite and ComplexType
by Anonymous Monk on Jul 06, 2006 at 03:37 UTC |