SoapClient->__construct()

参数

wsdl

URI of the WSDL file or NULL if working in non-WSDL mode.

options

An array of options. If working in WSDL mode, this parameter is optional. If working in non-WSDL mode, you must set the location and uri options, where location is the URL to request and uri is the target namespace of the SOAP service.

The style and use options only work in non-WSDL mode. In WSDL mode, they come from the WSDL file.

The soap_version option specifies whether to use SOAP 1.1, or SOAP 1.2 client.

For HTTP authentication, you may use the login and password options. For making an HTTP connection through a proxy server, use the options proxy_host, proxy_port, proxy_login and proxy_password. For HTTPS client certificate authentication use local_cert and passphrase options.

The compression option allows to use compression of HTTP SOAP requests and responses.

The encoding option defines internal character encoding. This option does not change the encofing of SOAP requests (it is always utf-8), but converts strings into it.

The classmap option can be used to map some WSDL types to PHP classes. This option must be an array with WSDL types as keys and names of PHP classes as values.

The trace and exceptions options are useful for debuging purpose.

add a note User Contributed Notes

Marius Mathiesen
01-Mar-2006 08:57


I kept having a problem using an HTTP proxy with SOAP. The proxy_port parameter has to be an integer, ie. "proxy_port"=>"80" won't work, you'll have to use "proxy_port"=>80.



HTH,

Marius

php at sowen dot de
22-Dec-2005 10:40


If you're using CLI and there are multiple IP addresses available for outgoing SOAP-requests, try this "secret" to set outgoing IP:



e.g. for local IP 10.1.4.71:



$opts = array('socket' => array('bindto' => '10.1.4.71:0'));

$context = stream_context_create($opts);

$client  = new SoapClient(null, array('location'=>'http://...','uri' => '...','stream_context' => $context));



You can also set other options for the stream context, please refer to this page:



Appendix M: http://www.php.net/manual/en/wrappers.php



Bye,

   Nils Sowen

fakko at users dot sourceforge dot net
25-Oct-2005 08:45


For development with wsdl you should disable wsdl caching because otherwise changes to the wsdl file will have no effect until soap.wsdl_cache_ttl expired!

bp
29-Aug-2005 01:19


The trace option IS documented, just not on this page. You need to have trace set to true in order to use the __getLast... methods.

jared at ws-db dot com
29-Aug-2005 05:31


If you connect to a SoapServer, that has been created with session persistence, you can access the server's session id via SoapClient->_cookies[<session_id_name>][0]. This property becomes available after your first client method call.



I have only tested this with session.use_cookies=1.

Jim Plush
19-Aug-2005 07:17


an undocumented feature -> setting a connection timeout



$client = new SoapClient($wsdl, array("connection_timeout"=>5));



ideally you'd have two timeouts set in your application one for how long it should take to actually connect to your remote host and a timeout for how long the socket connection should wait for a response from the server



the above addresses the time it takes to wait to connect to your host and this addresses the time to wait for a response



ini_set('default_socket_timeout', 180);



I would wrap this in a configuration option in case you distribute your package and different clients might need different timeouts when dealing with slow soap server responses.



// SET SOCKET TIMEOUT

        if(defined('RESPONSE_TIMEOUT') &&  RESPONSE_TIMEOUT != '') {

            ini_set('default_socket_timeout', RESPONSE_TIMEOUT);

        }

Arjan van Bentem
12-Aug-2005 02:31


When using HTTP basic authentication, PHP will only send the credentials when invoking the service, not when fetching the WSDL. 



To solve this, one needs to fetch the WSDL manually (or using PHP, of course!) and store it on the file system. Obviously, the first parameter for SoapClient(..) then needs to refer to that local copy.



Alternatively, the user annotations at http://nl3.php.net/manual/en/ref.soap.php state that one could encode the login and password into the URL as well.



See http://bugs.php.net/bug.php?id=27777

marcus at synchromedia dot co dot uk
12-Jul-2005 10:30


The trace and exceptions options are not well documented. Both are simple booleans, so you set them like so:



$sc = new SoapClient("http://www.example.com/my.wsdl", array('trace' => true, 'exceptions' => true));



I've not yet spotted trace doing anything particular, but exceptions is not just of interest for debugging as the docs suggest - it determines whether soap errors throw exceptions. The exceptions that it throws are of type SoapFault, which are documented elsewhere in these docs.

Jim Plush
12-Jul-2005 03:56


As of version 5.0.4 you can now dynamically change your location even if you're using a wsdl



<?php



$client = new SoapClient("http://some.host.net/wsdl/somefile.wsdl",array(

    "location" => 'myurl.com'));



?>



notice you can now use the "location" key. 

This means you can have the same wsdl file not define a location until runtime which is great if you have a development test site or if you distribute your files to other companies. 

Prior to this change you would have to ship a custom wsdl file to every client you had with their location hardcoded.

Brian Grayless
05-Mar-2005 06:30


Using a WSDL file is the way to go, however, for my particular application, the LOCATION:PORT needed to be dynamic so that my SOAP clients would be able to call a different service based on the client domain.



If you are using a WSDL, SoapClient() requires a URL direct to an actual URL and does not let you use a PHP file that outputs the dynamic WSDL XML in its stead. So, I ended up making a separate WSDL for each possible service needed and had to maintain them all if the service description changed.



Finally, after some fiddling, I was able to create a PHP page with the proper Mime type headers so that I could then trick SoapClient() to think that it was being passed a file with a ".wsdl" extension.



Example:



<?php



// filename: wsdl.php



header('Content-Type: application/xml; charset=UTF-8');

header('Content-Disposition: attachment; filename="filename.wsdl"');



$wsdl = 'path/wsdl_name.wsdl';



// read in file

$handle = fopen($wsdl, "r");

$wsdl_xml = fread($handle, filesize($wsdl));

fclose($handle);



// put code here to replace url and port in xml



echo $wsdl_xml;



?>



Now, in order to make this work, you can't just call a relative path to the file. I believe it has to go through Apache to properly set the mime type headers, etc... So you would use a full "http://....." address as the path to the wsdl.php file.



<?php



//... somewhere in your soap client code



$wsdl_loc = "http://yourdomain.com/wsdl.php";



$soap_client = new SoapClient($wsdl_loc, $client_param_array);



?>



Another, perhaps not so clean, way of achieving this would be to modify your .htaccess file in the directory where your WSDL file exists to force ".wsdl" files to run through the PHP engine. Add the following to your .htaccess:



AddType application/x-httpd-php .php .wsdl



You can then put dynamic PHP code snippets in your *.wsdl files to change whatever values you need to.



There are pros and cons to each solutions. The Mime solution probably taxes the system more as it has to read the file in every time a soap request is made. The htaccess solution makes it so you have to depend on either a modified .htaccess or Apache conf file.



Perhaps if you set the "soap.wsdl_cache_enabled", using ini_set(), to 1 (default), the caching will make it so it doesn't read the file every time for the Mime solution.

add a note

SoapClient->__construct()

说明

参数

范例