Closed (fixed)
Project:
Migrate Plus
Version:
8.x-2.x-dev
Component:
Plugins
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 May 2016 at 12:20 UTC
Updated:
25 Jul 2016 at 15:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
heddnThis would essentially depend on XML. Which has some working pieces already in migrate_plus and in migrate_source_xml.
Comment #3
mikeryanI'm on a project now that requires importing from a SOAP service, so I'll be looking at this over the next couple of weeks. At first glance, this would probably be independent from our existing XML support, building on the PHP SoapClient class instead.
Comment #4
mikeryanVery basic POC, known to work for exactly one service...
Comment #5
mikeryanYep, so responses aren't necessarily XML (my real-world scenario turns out to return an object containing an array of objects), so going to need a more flexible way to handle responses. Perhaps a SoapResponseParser plugin type - it's plugins all the way down!
Comment #6
mikeryanThis seems to work (so far) for my use case. For now, the different response types are hardcoded - the type-specific code is a line or two each, so introducing a plugin type seems overkill.
Comment #7
mikeryanI've completed implementing the migration from SOAP for my current project - setting to "Needs review", if anyone else is doing SOAP migration please give it a whirl.
Comment #9
mikeryanI've gone ahead and committed this - if anyone has any issues with it, please open a fresh issue.