I take it you are the author of Problem with combination of SOAP::Lite and Apache AXIS2, as I pointed out in that thread, SOAP::Lite does have difficulty with the WSDL generated for an Axis2 service but that can be worked around quite simply as I showed, it is perfectly possible to call the Axis2 getVersion service from SOAP::Lite and for whatever reason you weren't able or prepared to get it to work.

You seem to be refering to the shortcomings of Perl and SOAP::Lite with regard to SOAP interchangeably, but the bottom line is that perl knows nothing about SOAP and any support must come from a module such as SOAP::Lite, so any failing is in the module, not the language itself, it would be the same if we were talking about CORBA or EDIFACT, and the same is true of Java which requires an external library such as Axis to deal with web services.

SOAP::Lite certainly does have its shortcomings, not a few of which are related to its ability to handle WSDL in all possible cases, but of course it's entirely possible that the author of the module was either unaware of these cases (which I think is possibly quite likely with the Axis2 WSDL I've seen) or there have been higher priority things to implement, either way a bug report with an indication of the WSDL that isn't working properly to the author is far more likely to get results than moaning about it here, which doesn't really serve any purpose whatsoever.

/J\