Project

General

Profile

Actions

Feature #19791

closed

Use native SoapClient implementation of PHP5 only

Added by Marcus Krause over 15 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Extension Manager
Target version:
-
Start date:
2009-01-11
Due date:
% Done:

100%

Estimated time:
PHP Version:
5.2
Tags:
Complexity:
Sprint Focus:

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

10097.diff (227 KB) 10097.diff Administrator Admin, 2009-01-11 13:44

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #20611: deprecated function in class.nusoap.php in TYPO3 v.4.3alpha3ClosedBenni Mack2009-06-12

Actions
Related to TYPO3 Core - Bug #19558: Upload to TER behind proxy not possibleClosed2008-11-03

Actions
Actions

Also available in: Atom PDF