[php-src] Issue #8019: wsdl 2.0 support
| From: | veewee | Date: | Tue, 01 Feb 2022 17:18:38 +0000 |
| Subject: | [php-src] Issue #8019: wsdl 2.0 support | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-239413@lists.php.net to get a copy of this message | ||
Issue: https://github.com/php/php-src/issues/8019
Comment Author: veewee
@Ocramius, thanks for mentioning!
We recently started a new soap organization that aims for a replacement of ext-soap:
https://github.com/php-soap/
It is used as the SOAP implementation behind phpro/soap-client (and hopefully other projects in the
future)
Theoretically, it can do everything without ext-soap.
However, it is far from there yet.
(Especially encoding/decoding and WSDL parsing is missing - and will take a lot of time to get right
from my side)
I am not planning to add any SoapServer support at this moment.
This leaves out goetas' libraries as basically the only ext-soapless replacement I know off,
besides sending raw XML over HTTP yourself.
Last time I checked, it was not as performant in encoding / decoding compared to the built-in
SoapClient. I could be wrong here though!
**Unbundling ext-soap seems like a quite drastical decision at this point:**
There are MANY, MANY, MANY implementations relying on it to be there.
The reason why is because it is pretty much the only tool that solves SOAP, in a (buggy but) quite
decent way.
Just search for soap on packagist: most of them use ext-soap.
This list don't include any real business applications. At our company alone, I think we have
around 50-100 projects relying on it.
Removing or unbundling ext-soap will result in a lot of issues without any plug and play
replacement.
What would be the alternative for those users?