PHP SOAP Extension

I've tried to get the PHP soap extension working, but seems to be more than I can handle for now with the current services configuration.

I can do some extra code to get an automatic wsdl generation (php soap extension does not do this) on server construction (http://us.php.net/manual/en/function.soap-soapserver-construct.php) , but I can't bypass the services naming convention used up to now (http://us.php.net/manual/en/function.soap-soapserver-addfunction.php) SoapServer:addFunction requires a valid php function, and services do not comply with this (node.load, etc.. )

So it's going to be postponed to a future work since we still don't have the nusoap working neither. I'll focus no nusoap for now, just because it's easy and quick while I find a solution for the php soap extension.

Hi

I´ve got my own SOAP-Server Module working with the native PHP5 extension.
It doesn´t generate WSDL Files yet but I´m working on...

May be it´s interessting to dev with others...

Greets

Uhu

I have been reading online that nusoap has conflicts with the native php5 extension, and there's even a nusoap for php5 on google code.

So I think this feature would be very important to have... any news on this?

Nevermind I've seen that this problem is already accounted for in the module, so ignore my previous concern about conflicts with the native php5 extension... (sorry!)

ilo @ #1, I agree with you that the naming convention should be changed (at least on the SOAP part). I try to access those methods from a Spring Framework-based Java Application. As usual, I set up a dynamic AOP proxy and a Service Interface but it's not possible to handle those methods with a dot in it...

Any progress on this?