Open feamsr00 opened 8 years ago
Note: If I instead consume the WSDL from a second request to the echoed XML (eg "../Service?wsdl") it works. But, this couldn't be by design. Having to spin up full tcp\httpd\php\framework machinery just to get at data that is a few JMPs away is ludicrous, right?
Giving this issue a bump, was setting up a SOAP integration but ran into this issue which is now rather blocking.
This repository has been closed and moved to laminas/laminas-soap; a new issue has been opened at https://github.com/laminas/laminas-soap/issues/20.
Hi There,
I'm having a problem when using Soap\Server() but I'm not 100% sure if this is a framework bug or if I'm not using the API correctly (as the documentation is a little sparse on the matter)
If I construct Soap\Server() with WSDL generated from Soap\AutoDiscover->generate(), a very strange thing happens. Upon calling Server->handle(), the framework will bail immediately and prints the following (regardless of ::setReturnResponse) :
In addition, anything outputted previously will appear inside a "detail" element appended to the "Fault" element.
What could be causing this?
I look forward to your thoughts. Thanks in advance.
PS I notice there are no bugs here, should I be making this bug somewhere else?