Soap\Server::handle() never returns

[weierophinney]

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) :

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
        <SOAP-ENV:Fault>
            <faultcode>SOAP-ENV:Server</faultcode>
            <faultstring>SoapServer::SoapServer(): Invalid parameters</faultstring>
        </SOAP-ENV:Fault>
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

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?

---

Originally posted by @feamsr00 at zendframework/zend-soap#6

[weierophinney]

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?

---

Originally posted by @feamsr00 at zendframework/zend-soap#6 (comment)

[weierophinney]

Giving this issue a bump, was setting up a SOAP integration but ran into this issue which is now rather blocking.

---

Originally posted by @ghost at zendframework/zend-soap#6 (comment)

[SalvatorePollaci]

UP

[Xerkus]

Proper way to bump the issue is by opening the PR

[weierophinney]

@SalvatorePollaci Or by providing information on how to reproduce.

There's no information here on how the author was setting up the Autodiscover or Server instances, or what types of classes or functions were being attached; it's entirely possible there are errors.

Based on the comments they posted later, it sounds very much like they could be calling code that has side effects in terms of output that would cause the instances to raise error conditions.

[weierophinney]

This package is considered feature-complete, and is now in security-only maintenance mode, following a decision by the Technical Steering Committee.
If you have a security issue, please follow our security reporting guidelines.
If you wish to take on the role of maintainer, please nominate yourself

If you need an actively developed SOAP client, we recommend phpro/soap-client.