SOAP clients kills SOAP server [#605496]

Hi,

I've been playing with SOAP for the better part of the day. It's neat. And the Drupal modules make it so easy to set up something fast.
For testing purposes, I've configured a local drupal installation (virtual host) with Services and the SOAP server module (http://drupal.org/project/soap_server) The latter translates all the services (including the ones I'm programming myself) as SOAP listeners to the outside world. If I go to site.lan/services/soap I'll get a nice SOAP/WSDL page with all the exposed calls.

Then I installed the SOAP client on the same site. (Didn't feel like setting up a seperate virtual host and stuff just for testing.) That effectively kills the SOAP server module.

* The SOAP server settings page at services/settings/soap returns a blank page
* the SOAP server endpoint at services/soap returns a blank page

Don't get any PHP errors or anything. It's just not there. As soon as I disable SOAP client, the server functions back like it should.

Could have posted the same issue on the SOAP server project... don't know which one is the culprit.

Comments

Comment #1

ilo CreditAttribution: ilo commented 15 October 2009 at 22:32

Actually I had expected this to happen. This is the main reason to push the issues:

#581202: Make nuSOAP library location configurable
#408360: NuSOAP project code should not be in CVS

The problem with soap_client beta version could be that nusoap is being included once, and later again by soap_server (could be other nusoap version also), getting these odd results. soap_client dev version now only loads nusoap if it has to be used, so I guess this would do (If you could test, it would be great and would also help to identify the problem.. tip: remember to delete old soapclient folder, unzip the -dev version and do update.php)

Since some web service calls require the use of nuSOAP by the other side (server or client) probably a wrapping function for both (soap_client and soap_server) is the final solution.

So, could you give a try with the -dev version of soapclient? once you run update.php, go to soapclient settings and put the folder of the nuSOAP library used by the soap_server module.

Thanks for your report.

Comment #2

netsensei CreditAttribution: netsensei commented 16 October 2009 at 07:45

Hi,

I installed -dev version next to soap_server on drupal 6.14. The new 'nuSOAP location' setting picked up the nu_soap lib included through soap_server nicely. The SOAP server is now functioning as it should with soap_client.

So this gets a thumbs up. Looking forward to see a stable release!

Thanks!

Comment #3

ilo CreditAttribution: ilo commented 16 October 2009 at 10:22

Status:

Active

» Fixed

Good to know :)

Thanks for the test netsensei. I'll keep the 'remove and redesign' issues regarding crypto, write some simpletest cases and that would provide the path to the stable release.

Please, as I guess you will be interested in the client module upgrades, I kindly suggest you to subscribe to the issue queue (all issues) in this module so you will recieve email for any movement in the module, and I and others will be able to hear your suggestions to the proposed plan.

Thanks again.