Create a configuration form to define the SOAP interface, including php's builtin soap support.

Comments

robloach’s picture

Status: Active » Needs review
StatusFileSize
new14.84 KB
new23.52 KB

How's this? Provided is both the patch and a screenshot of the configuration page. I could put it in if you want.

ilo’s picture

StatusFileSize
new15.52 KB

I've modified your patch to take care about php_soap loaded extension. If the php.so/dll is loaded the module will stop working.

I'm going to modify the soap functions for both, php_soap and nusoap engines, so expect module fails these days.

I will not commit yet, so feel free if you want to commit anything.. I'll do a merge in the end.

Thanks Rob!

robloach’s picture

Status: Needs review » Fixed

The management of having it work with PHP's core SOAP Server will have to be handled by a different issue.

ilo’s picture

Version: » 5.x-1.x-dev
Status: Fixed » Reviewed & tested by the community
StatusFileSize
new5.49 KB

I'm going to apply this patch (none of the previous patches was commited) to reduce the errors reported when php soap extension is loaded and you try to run a server with nusoap.

robloach’s picture

Status: Reviewed & tested by the community » Needs work

There are some conflicts introduced by this patch. I changed some of the way it worked in the previous patch to work nicer with t(). This seems to back track to how it was before. What we have to do is create an entirely new patch with new code which just builds upon what's in the DRUPAL-5 branch right now.

robloach’s picture

Why is there a conflict with the SOAP extension anyway? Is there anyway we can use NuSOAP with the extension loaded? extension_loaded('soap') returns TRUE on this end, and I have absolutely no problem using NuSOAP....

ilo’s picture

I'm confused, I just downloaded the module using cvs client, modified and create the patch agains the repository. It should not conflict.. :( I don't know what I did wrong.

About the nusoap-phpsoap extension problems..

In any case, I'm having problems with nusoap if I enable the soap module in a windows environment. In linux, I've soap support builtin, instead of module, so I can't unload, and the soap code gets the php's internal argument layout instead of the nusoap.

I'm pretty sure this should not only happend to me.. I'm using a very regular (easyphp) lamp installation for development, and a debian server with apache2 packaged binary (apt-get downloaded).

robloach’s picture

Like the changes to #description and $status.... I changed those so that it would work nicer with the call to t().

niklp’s picture

Can anyone comment a little more on exactly what this does? And is there any progress on here?

I have a need for a SOAP interface in the very near future and I would like to keep up with what's goin' on.

robloach’s picture

Hey Nik! This patch lets you configure where NuSOAP is located, because right now it assumes it's in a subdirectory of the soap_server path.

niklp’s picture

Patch it up then, Beavis! :p