use_soap_error_handler
Make sure to prefix constructor calls with @ and catch SoapFault exceptions, otherwise you risk having the php interpreter exit/die on simple network issues.
Robust sample code by Rasmus from http://bugs.php.net/bug.php?id=47584
<?php
try {
$x = @new SoapClient("non-existent.wsdl",array("exceptions" => 1));
} catch (SoapFault $E) {
echo $E->faultstring;
}
echo "ok\n";
?>
La clase SoapClient
Introducción
La clase SoapClient proporciona un cliente para servidores » SOAP 1.1, » SOAP 1.2. Puede ser usada en modo WSDL o modo no-WSDL.
Clases sinopsis
SoapClient
{
/* Métodos */
public string __doRequest
( string $request
, string $location
, string $action
, int $version
[, int $one_way = 0
] )
public mixed __soapCall
( string $function_name
, array $arguments
[, array $options
[, mixed $input_headers
[, array &$output_headers
]]] )
}Table of Contents
- SoapClient::__call — Llama a una función SOAP (obsoleto)
- SoapClient::__construct — Constructor de SoapClient
- SoapClient::__doRequest — Realiza una petición SOAP
- SoapClient::__getFunctions — Devuelve una lista de todas las funciones SOAP disponibles
- SoapClient::__getLastRequest — Devuelve la última petición SOAP
- SoapClient::__getLastRequestHeaders — Devuelve los encabezados SOAP de la última petición
- SoapClient::__getLastResponse — Devuelve la última respuesta SOAP
- SoapClient::__getLastResponseHeaders — Devuelve los encabezados SOAP de la última respuesta
- SoapClient::__getTypes — Devuelve una lista de los tipos SOAP
- SoapClient::__setCookie — El propósito de __setCookie
- SoapClient::__setLocation — Define la localización del servicio Web a utilizar
- SoapClient::__setSoapHeaders — Define los encabezados SOAP para las subsiguentes llamadas
- SoapClient::__soapCall — Llama a una función SOAP
- SoapClient::SoapClient — Constructor de SoapClient
add a note
User Contributed Notes
SoapClient
tlk
19-May-2011 01:35
jjlopez
09-Mar-2011 07:36
If you are making soap calls in WSDL mode , and the address of your web service includes a port different from 80 (like http://my_ip_address:8080//service.asmx?wsdl), the WSDL file is fetched correctly, but all subsequent requests are made without any port in the host field. This causes a SoapFault exception when trying to call any of the service’s methods.
You need to redefine the soapClient class and force the port in each call.
See this example:
http://www.victorstanciu.ro/php-soapclient-port-bug-workaround/
hugues at zonereseau dot com
18-Feb-2011 05:17
When you need to connect to services requiring to send extra header use this method.
Here how we can to it with PHP and SoapClient
<?php
class exampleChannelAdvisorAuth
{
public $DeveloperKey;
public $Password;
public function __construct($key, $pass)
{
$this->DeveloperKey = $key;
$this->Password = $pass;
}
}
$devKey = "";
$password = "";
$accountId = "";
// Create the SoapClient instance
$url = "";
$client = new SoapClient($url, array("trace" => 1, "exception" => 0));
// Create the header
$auth = new ChannelAdvisorAuth($devKey, $password);
$header = new SoapHeader("http://www.example.com/webservices/", "APICredentials", $auth, false);
// Call wsdl function
$result = $client->__soapCall("DeleteMarketplaceAd", array(
"DeleteMarketplaceAd" => array(
"accountID" => $accountId,
"marketplaceAdID" => "9938745" // The ads ID
)
), NULL, $header);
// Echo the result
echo "<pre>".print_r($result, true)."</pre>";
if($result->DeleteMarketplaceAdResult->Status == "Success")
{
echo "Item deleted!";
}
?>
jeffmixpute
24-Jan-2011 11:15
Simple php client and server:
Client:
<?php
// bind SOAP/Client.php -> path of the php file
require_once "SOAP/Client.php";
// URI delivered to web service
$sc = new SOAP_Client("http://localhost/SOAP/Server.php");
// start call function to use the function of the Web Service
$parameter = array();
$result = $sc->call ("now", &$parameter, "urn:TimeSerivce");
// print result
print $result."\n";
?>
Server:
<?php
// bind PEAR::SOAP
require_once "SOAP/Server.php";
$skiptrace =& PEAR::getStaticProperty('PEAR_Error', 'skiptrace');
$skiptrace = true;
// program service class
class TimeSerivce {
public function now () {
date_default_timezone_set("Europe/Berlin");
return (date ("H:i"));
}
}
// web service classs develop
$service = new TimeSerivce();
// server develop
$ss = new SOAP_SERVER();
// assing the name to the service
$ss->addObjectMap($service, "urn:TimeSerivce");
// Einstellung, dass POST-Daten an den Service weiter gegeben werden
// preferene to forword POST data to the service
$ss->service ($HTTP_RAW_POST_DATA);
?>
fourat dot zouari at tritux dot com
20-Jun-2009 03:08
In addition to the KeepAlive trick which is a "server-side" modification, on the "client side" default_socket_timeout should be increased from its default value (60) when you deal with ~slow SOAP servers.
As for the KeepAlive, if creating a new separate vhost for the soap api is not possible, you can add this to your existing vhost: BrowserMatch "^PHP-SOAP" nokeepalive
where PHP-SOAP is the agent name of your soap client, if you dont know what agent name your client use, just checkout the access.log of your apache.
peter dot hansen at fastit dot net
01-May-2009 01:57
When you get errors like:
"Fatal error: Uncaught SoapFault exception: [HTTP] Error Fetching http headers in"
after a few (time intensive) SOAP-Calls, check your webserver-config.
Sometimes the webservers "KeepAlive"-Setting tends to result in this error. For SOAP-Environments I recommend you to disable KeepAlive.
Hint: It might be tricky to create a dedicated vhost for your SOAP-Gateways and disable keepalive just for this vhost because for normal webpages Keepalive is a nice speed-boost.