Feature #19791
closed
Use native SoapClient implementation of PHP5 only
100%
Description
Currently EM uses native SoapClient implementation of PHP5's extension soap. However, there are fallbacks to PEAR:Soap and nusoap library. Library nusoap is even embedded. There is even the possibility to configure which implementation will be choosed.
The fallbacks were necessary in PHP4, but with PHP5 there is a native SoapClient implementation.
The patch removes nusoap library, fallback switches and methods call wrappers.
Why:
- we now have a native implementation in PHP5
- Soap calls in TYPO3 core are only made in EM; the adapter is within module EM; so it was never intended to provide a Soap Client implementation for TYPO3 extensions
- we wouldn't need to maintain the embedded library and react on API modifications in third-party implementations (nusoap,PEAR)
- any new options to set would need us to write or modify wrapper methods (missing Proxy support)
(issue imported from #M10097)
Files
Updated by Xavier Perseguers almost 13 years ago
- Status changed from Accepted to Needs Feedback
This patch has been committed long ago, why is this issue still open?
Updated by Xavier Perseguers almost 13 years ago
- Target version changed from 1081 to 1238
Updated by Oliver Hader almost 13 years ago
- Target version changed from 1238 to 1281
Updated by Xavier Perseguers almost 13 years ago
- Target version changed from 1281 to 4.6.0-beta1
Updated by Stefan Neufeind almost 13 years ago
TYPO3 seems to use only (!) the native php-soap-implementation starting with TYPO3 v4.5.0. No mentioning of nusoap or PEAR soap anymore. Only php-soap is called in typo3/sysext/em/classes/connection/class.tx_em_connection_soap.php
There is nusoap in 4.3 and 4.4. But we can't remove them from there :-)
Close this issue?
Updated by Xavier Perseguers almost 13 years ago
- Status changed from Needs Feedback to Closed
- % Done changed from 0 to 100
Updated by Ernesto Baschny almost 11 years ago
- Target version deleted (
4.6.0-beta1)