Active
Project:
Web service client
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 May 2014 at 18:33 UTC
Updated:
6 Jan 2015 at 22:11 UTC
Jump to comment: Most recent
Comments
Comment #1
dman commentedUsing the web service test module includes a (silent) feature to 'flush' the WSDL cache each request - FYI.
Comment #2
alfaguru commented+1 for this. Once a SOAP web service has been added there's no obvious way to update its stored definition from the WSDL other than by deleting and recreating it, which if it's been added to a feature is long-winded to say the least.
Flushing the WSDL cache won't change the definition stored, will it? So that'll still be out of step with the remote.
Comment #3
dman commentedYeah you are right, flushing the WSDL only affects a PHP-level cache thing.
As pretty much any change that may happen to the remote service could include a full rewrite : operations or datatypes may be added, deleted or changed during a refresh - it is pretty necessary to delete the entire service and re-initialize it from scratch each time.
I did that 10 times in succession last week when testing a change. Wasn't too hard with the browser memory remembering my endpoint URL in the textfield, but it's true a single button would have saved me three clicks each time...
Comment #4
alexku commentedWe are using following snippet in our current project:
CAUTION: this wipes out any custom changes on each submit of a specific service
I could create a patch adding a checkbox to service configuration form. If set, service configuration would be refresh on submit. Would this be useful?
Comment #5
joelpittetThanks @alexku, that seemed to work well. Just had to update it a bit so that features update didn't try to override it.