You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 31, 2020. It is now read-only.
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) :
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?
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?
The text was updated successfully, but these errors were encountered: