Re^2: Problem with combination of SOAP::Lite and Apache AXIS2

I doubt. Last night, I tried to write a AXIS client to call this service provided through AXIS2, and it worked. Now I clearly intend to believe that the problem is with SOAP::Lite.

One of the problem with SOAP::Lite is that it was not developed according to a high standard. Reading the document, you will see that, there are many places saying things like "this is not supported, and that is not supported".

For me, the solution is to get rid of Perl, and that's what I am going to do.

Comment on Re^2: Problem with combination of SOAP::Lite and Apache AXIS2

Replies are listed 'Best First'.
Re^3: Problem with combination of SOAP::Lite and Apache AXIS2 by gellyfish (Monsignor) on May 18, 2006 at 16:01 UTC
I'm sure the authors of SOAP::Lite will be delighted with your patches. I'm not quite sure what your beef is, you have ignored my inquiry as to what your client code looked like and simply decided that SOAP::Lite doesn't work at all. I think there is a problem with parsing the WSDL that axis2 generates, but this is partially because it exercises a number of features that are axis specific. Anyhow SOAP::Lite will work fine with that service (and I have installed axis2 to test this), this code works as expected for me: `use SOAP::Lite; + my $soap = SOAP::Lite->new(); + $soap->uri('http://axisversion.sample/xsd'); $soap->service('http://localhost:8080/axis2/services/version?wsdl'); + + print $soap->getVersion();` [download] /J\	[reply] [d/l]
Re^4: Problem with combination of SOAP::Lite and Apache AXIS2 by Anonymous Monk on May 18, 2006 at 17:23 UTC
Something special to AXIS, oh, then that's not SOAP. Love what you have said.	[reply]
Re^4: Problem with combination of SOAP::Lite and Apache AXIS2 by Anonymous Monk on May 22, 2006 at 20:01 UTC
Your way gives this error: `Transport is not specified (using proxy() method or service descriptio +n)` [download]	[reply] [d/l]