Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
Is there any plans for D7 version of this module?
Comment | File | Size | Author |
---|---|---|---|
#11 | 1073874_soapclient_d7_port.patch | 6.09 KB | greggles |
Comments
Comment #1
7wonders CreditAttribution: 7wonders commentedAlso looking for a dedicated soap client for drupal 7
Comment #2
mandreato CreditAttribution: mandreato commentedSubscribe
Comment #3
jrsinclair CreditAttribution: jrsinclair commentedI would really love to see a Drupal 7 version of this module too. It looks as though the developer's gone dark though. I will be looking into the Services module instead.
Comment #4
jrsinclair CreditAttribution: jrsinclair commentedOn further reading, it looks like the Services module won't act as a client, so I will be looking at this module again.
Comment #5
ah0 CreditAttribution: ah0 commentedhey guys anyone tried this:
http://drupal.org/project/wsclient
highly recommended
Comment #6
jaxxed CreditAttribution: jaxxed commentedah0: I took a quick look at wsclient, but it is described as a 'rules' implementation. Would it be more appropriate than this module? and is it a good drp7 implementation?
Drupal 7 mod highly desireable. I'll start on one now pending response from ah0 ... but I'd appreciate more feedback on what to bring along to DR7 and what to change.
Here are a list of things I see on my 5 minute analysis:
1 - Libraries API for nusoap?;
2 - Removal of global code (move to hook_init or something);
3 - Move more inline functions and global object variable to the drupalSoapClient class (global var, connect and parse methods, and utility methods such as array_to_object)
4 - Separate admin & test cases into include;
There is of course standard drp6->drp7 investigation involved, but on my quick investigation (not a lack of 6->7 experience) there isn't much to worry about.
Comment #7
jaxxed CreditAttribution: jaxxed commentedRE: wsclient -> it does look interesting. It's a DRP7 implementation and looks to have features support (which could be very handy.)
Comment #8
ah0 CreditAttribution: ah0 commented@ jaxxed
I tried the wsclient on a project and it was quite responsive.
It's more than just a basic web service client due to its integration with the Rules. you basically can do anything that comes to mind with this as it allows to create data structures and pull in the web service responses into the data structures and then using the Rules either pass them to nodes or other modules. You could also use something like a Rules scheduler to schedule when to run the client.
also if mapping the data structures to nodes, then you could use Views to see the results of data pulled from the web service responses.
It's a pretty neat tool and works quite reliably under D7.
The only part that's lacking in my view is limited documentation and examples, so it's more of self-effort to figure out how it works.
other comments on wsclient ?
Comment #9
kika CreditAttribution: kika commentedsubcribing
Comment #10
gregglesI'm trying this out now.
One thing - I may remove support for nusoap. Does anyone feel strongly about that?
Comment #11
gregglesAnd, here's a patch. I avoided doing any cleanup work in this so that could be handled separately.
I also couldn't get soapclient_find_nusoap_library to actually work, but I guess most people don't want nusoap.
Comment #12
gregglesI made the port thinking it might help me in calling a soap service. Turned out there were other issues that were my problem.
I wonder how relevant this code is given that Drupal 7 requires php 5 and that this library is mostly useful if another module wants to make soap calls AND can't know reliably whether it will be using nusoap or the built-in function.
I suggest that folks looking for the D7 version of this module try to use the php soapclient directly http://php.net/manual/en/class.soapclient.php