SOAP or WSDL

No plans from the side of the maintainers ATM.

Yes, that's straightforward to do. I recommend working off the example of some of the existing parsers in Feeds' plugins/ directory.

Not an option for me :)
I needed to fetch a document from a remote server that I've got no control over.

So... here's a functional SOAP fetcher. (I fiddled with Feeds XPath Parser for the parsing part.)
It depends on the Soap client module.

For completeness sake: put this somewhere in your own module:

/**
 * Implementation of hook_feeds_plugins().
 */
function YOURMODULE_feeds_plugins() {
  $info = array();
  $info['SOAPFetcher'] = array(
    'name' => 'SOAP Fetcher',
    'description' => 'Fetches SOAP feed.',
    'handler' => array(
      'parent' => 'FeedsFetcher', // A plugin needs to derive either directly or indirectly from FeedsFetcher, FeedsParser or FeedsProcessor.
      'class' => 'FeedsSOAPFetcher',
      'file' => 'FeedsSOAPFetcher.inc',
      'path' => drupal_get_path('module', 'YOURMODULE'),
    ),
  );
  return $info;
}

So... where would people want to put this?
The feeds distribution?
soapclient?
It just seems too small to me, to warrant its own module. (It's purely "copy-paste, modify, test" code.) Not that I'd be against it, per se... :)

I'd rather see this in a separate module, I don't want to maintain it.

subscribing - looks useful!

subscribing

I couldn't manage to set up a parser on feeds. Is there any example for this?

subscribing.

I hacked roderik's code a to remove the dependency on the soapclient module, as I don't think the abstraction layer it provides is still necessary now in the days of PHP 5, and PHP 4 and NuSOAP are dead AFAIK :) In my version it uses PHP 5's soap client straight to the point.

I am still thinking about how to handle best the final outcome of the SOAP call, as what you got left eventually are PHP strings / objects / arrays / ..., depending on what the SOAP server has sent you back. I currently just return the full http SOAP response body (and not just the result contained in it) so that's in any case parseable with the xpath parser, but I am also thinking about adding an option to switch output formats. Two additional ones off the top of my head:

• just the SOAP result, if it's a string (that is what Roderik's initial work did if I understood the code right)
• a JSON respresentation of the soap result (really easy with PHP 5's JSON functions), which is parseable again with the JSONPath parser

Does there exist some kind of Feeds parser already that provides a xpath/querypath/jsonpath-like syntax to navigate over PHP arrays/objects/...? In PHP userland I was only able to find CakePHP's Set::extract() (http://book.cakephp.org/view/1501/extract) so far by using my favorite search engine. Looks cool at first sight. I might give it a try.

@roderik, fine for you if I initialize a new project here on DO for the SOAP fetcher? I will of course mention you as the author of the initial code. Unless you feel like taking the lead of this yourself... :)

@Cyberwolf: fine with me - I am not finding the time.

Better, even - because I just whipped this up from my Feeds module knowledge and some copypaste from soapclient... but I am not using either of them extensively. It'd be hard for me to give support on the SOAP part of things.

Any update on separate module for SOAP fetcher?

subscribing

I just returned from holidays, will initialize a new project asap.

Subscribe

@Cyberwolf, any idea when you'll have a project (or sandbox) set up?

Hi,

I initialized a Sandbox project here: http://drupal.org/sandbox/Cyberwolf/1288548

Great, thank you!!!

This looks great, exactly what i need for a project i'm working on. I will be following the sandbox project closely.

i need it too - thanks

subscribing

Does anyone know of any updates regarding this?

Looks like magico forked my sandbox already into a full project: http://drupal.org/project/feeds_soap

Here's my new sandbox project "Feeds FetchXML" witch is using library from http://code.google.com/p/php-dynamics-crm-2011 for integration with CRM 2011 and claim based authentication. Feel free to test it.

http://drupal.org/sandbox/petria/1916146

It's already in production on our site.