Closed (duplicate)
Project:
Web service client
Version:
7.x-1.0-alpha3
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 Apr 2011 at 06:32 UTC
Updated:
14 Mar 2015 at 11:43 UTC
Jump to comment: Most recent
Comments
Comment #1
klausiYep, you will want to disable the WSDL cache during development - but you want the cache on production environments, because then you don't need to load the WSDL file for every SOAP request, which is quite a performance gain.
Maybe we should document this?
Comment #2
RikD commentedThanks for the replay, maybe it is useful to put it into the documentation.
Is the way I do it the easiest way to do it or are there other options to turn of the cache during development, maybe some build-in option :P.
By the way. Wwsclient easy to use plugin. My compliments for the development team..
Comment #3
tuccio commentedIf you don't want to disable the wsdl cache but need clearing it occasionaly, you can just delete the wsdl--* files from the php temp_dir (usually /tmp). Perhaps this would be a useful option to add to the module?
Comment #4
dman commentedFYI, I've just pushed this to the wsclient_tester module.
If you use -dev (or the next release to come) and use the wsclient tester on the WSDL, it will flush your cache each time you make a request.
This did my head in this evening, and I figure that people who test want it flushed.
It will have no effect on day-to-day running, but belongs in the test zone.
Comment #5
dman commentedPushing this to #2269661: Refresh Web Service because, although that issue is newer, it has a suggested fix (no patch yet) and identifies that it's not just about PHP WSDL caching - it's about how the web service definition imported and remembered by wsclient itself needs a full rebuild when a service changes during development.
Comment #6
neuron1122 commenteduse can use this instead of turing off the cacshe
$client = new SoapClient('http://somewhere.com/?wsdl', array('cache_wsdl' => WSDL_CACHE_NONE) );