My first web service Client
Posted: Wed Apr 07, 2010 5:34 am
This week my bosses have decided we have to change our entire product so that it just queries a web service (
) and as I don't know anyone who even knows what a web service is (
) and it has to be completed by tomorrow I'm back on here asking questions.
Basically the main question I have is, what tools should I use? I know this has been asked a number of time on here (I think I've read a million posts this morning) but the answers always seem a little vague.
To help things along here's the situation. I will have to query a .NET WSDL web service which has not been built yet, but some test ideas were/will be available for test connections
I have tried the following, all with varied results.
cURL -> Was nice and easy when connecting to a third party service but the service I am connecting to requires the header M-POST and it all got complicated.
PHP SOAP Library -> Connected to the service and got a huge nested object in return, which is basically unusable.
PEAR-SOAP -> Have not yet tried this, but hear it's pretty much been depreciated due to the SOAP library.
Nu-SOAP -> Read about this in an old book, is it even worth looking at or has it died a death?
Which one of these is the standard? Should I just look at using a framework to make my life easy?
One last question, the web service name dosen't end with .wsdl. Does this make a difference to PHP?
Thanks for reading. Any nudge in the right direction would be helpful
EDIT: Just found WSF/PHP. Is this in common usage, or should I stick to something like cakePHP/Zend/Symphony and such?
Basically the main question I have is, what tools should I use? I know this has been asked a number of time on here (I think I've read a million posts this morning) but the answers always seem a little vague.
To help things along here's the situation. I will have to query a .NET WSDL web service which has not been built yet, but some test ideas were/will be available for test connections
I have tried the following, all with varied results.
cURL -> Was nice and easy when connecting to a third party service but the service I am connecting to requires the header M-POST and it all got complicated.
PHP SOAP Library -> Connected to the service and got a huge nested object in return, which is basically unusable.
PEAR-SOAP -> Have not yet tried this, but hear it's pretty much been depreciated due to the SOAP library.
Nu-SOAP -> Read about this in an old book, is it even worth looking at or has it died a death?
Which one of these is the standard? Should I just look at using a framework to make my life easy?
One last question, the web service name dosen't end with .wsdl. Does this make a difference to PHP?
Thanks for reading. Any nudge in the right direction would be helpful
EDIT: Just found WSF/PHP. Is this in common usage, or should I stick to something like cakePHP/Zend/Symphony and such?