Hello Andrew,
what kind of op-code cache are you using? I have heard from people that this what you are describing is happening with e-accelerator, personally I never had a problem with APC. However I should really update the documentation, the WSDL is not something to be generated dynamically upon each request, static serving is much better (of course if you keep it in sync with your real server implementation). greetings, Benjamin On Fri, 9 Apr 2010 14:28:23 -0400, Andrew Ballard <[email protected]> wrote: > On Fri, Apr 9, 2010 at 1:00 PM, Andrew Ballard <[email protected]> wrote: >> I set up a very basic client and server using autodiscover to try out >> SOAP in ZF. For some reason, all of the functions are returning NULL. >> The problem seems to be that the <operation> node in each of the >> <portType> nodes is missing an <output> on successive requests. They >> are in the WSDL the first time I run the autodiscover after changing >> the model. It also seems that the <documentation> node contains the >> name of the method instead of the description in the header block. >> >> To test, I added a new method to the model and then saved the WSDL >> generated by autodiscover on the next request. I then changed the WSDL >> in both the client and server to point to this static XML file -- all >> the methods returned exactly what was expected. >> >> Does anyone have any idea why Zend_Soap_AutoDiscover is doing this? >> >> Andrew >> > > I think I may have figured this out during lunch. I think the issue is > the opcode caching on the server. Whenever the page is updated, PHP > grabs the new version from source code -- including comments. > Subsequent requests would come from the cache, and since it is just > opcode it doesn't have any comments to direct Zend_Soap_AutoDiscover. > > Andrew
