Класс SoapFault
You may use undocumented and invisible property $e->faultcode to access string version of $code. Because standard $e->getCode() does not work:
$e = new SoapFault ( «test» , «msg» );
var_dump ( $e -> getCode ()); // prints «0»
var_dump ( $e -> faultcode ); // prints «test»
?>
Also you may use namespaced fault codes:
$e = new SoapFault (array( «namespace» , «test» ), «msg» );
?>
— see ext/soap/soap.php, PHP_METHOD(SoapFault, SoapFault). To access the namespace, use $e->faultcodens
A bit more digging in ext/soap/soap.c and the set_soap_fault function reveals the other undocumented properties from the constructor:
try throw new SoapFault ( ‘code’ , ‘string’ , ‘actor’ , ‘detail’ , ‘name’ , ‘header’ );
> catch ( Exception $ex ) var_dump ( $ex -> faultcode , $ex -> faultstring , $ex -> faultactor , $ex -> detail , $ex -> _name , $ex -> headerfault );
>
?>
I’ve decided to post this since it may be helpful, I’ve spend a couple of days trying to do this.
In order to use wsdl’s specified faults with complex types, i.e:
(xsd:schema namespace, ns1 = target namespace)
You have to specify the response in the detail parameter as an array corresponding the tag names.
function operationTest ( $request_param . )
// .
$array_details = array( «detail1» => «Explanation 1» , «detail2» => «Explanation 2» );
return new SoapFault ( «Server» , «example fault string» , null , $array_details , «FaultSpecified» );
$server = new SOAPServer ( «handmade.wsdl» );
$server -> addFunction ( «operationTest» );
$server -> handle ();
?>
that should respond something like this:
is_soap_fault
Эта функция полезна для проверки неудачи вызова SOAP, но тогда, когда не используются исключения. Для того, чтобы её использовать, создайте объект SoapClient с опцией exceptions , равной нулю или false . В этом случае метод SOAP вернёт специальный объект SoapFault , который инкапсулирует детали ошибки (код ошибки, строка ошибки, получатель и детали).
Если опция exceptions не установлена, то вызов SOAP будет выбрасывать исключение в случае возникновения ошибки. Функция is_soap_fault() проверяет, является ли переданный параметр объектом SoapFault .
Список параметров
Возвращаемые значения
Возвращается true в случае возникновения ошибки и false в противном случае.
Примеры
Пример #1 Пример использования функции is_soap_fault()
$client = new SoapClient ( «some.wsdl» , array( ‘exceptions’ => 0 ));
$result = $client -> SomeFunction ();
if ( is_soap_fault ( $result )) trigger_error ( «Ошибка SOAP: (faultcode: < $result ->faultcode > , faultstring: < $result ->faultstring > )» , E_USER_ERROR );
>
?>
Пример #2 Стандартный метод SOAP для сообщений об ошибках — это исключения
try $client = new SoapClient ( «some.wsdl» );
$result = $client -> SomeFunction ( /* . */ );
> catch ( SoapFault $fault ) trigger_error ( «Ошибка SOAP: (faultcode: < $fault ->faultcode > , faultstring: < $fault ->faultstring > )» , E_USER_ERROR );
>
?>
Смотрите также
SOAP
PROBLEM (with SOAP extension under PHP5) of transferring object, that contains objects or array of objects. Nested object would not transfer.
SOLUTION:
This class was developed by trial and error by me. So this 23 lines of code for most developers writing under PHP5 solves fate of using SOAP extension.
/*
According to specific of organization process of SOAP class in PHP5, we must wrap up complex objects in SoapVar class. Otherwise objects would not be encoded properly and could not be loaded on remote SOAP handler.
Function «getAsSoap» call for encoding object for transmission. After encoding it can be properly transmitted.
*/
abstract class SOAPable public function getAsSOAP () foreach( $this as $key =>& $value ) $this -> prepareSOAPrecursive ( $this -> $key );
>
return $this ;
>
private function prepareSOAPrecursive (& $element ) if( is_array ( $element )) foreach( $element as $key =>& $val ) $this -> prepareSOAPrecursive ( $val );
>
$element =new SoapVar ( $element , SOAP_ENC_ARRAY );
>elseif( is_object ( $element )) if( $element instanceof SOAPable ) $element -> getAsSOAP ();
>
$element =new SoapVar ( $element , SOAP_ENC_OBJECT );
>
>
>
class PersonList extends SOAPable protected $ArrayOfPerson ; // variable MUST be protected or public!
>
class Person extends SOAPable //any data
>
$client =new SoapClient ( «test.wsdl» , array( ‘soap_version’ => SOAP_1_2 , ‘trace’ => 1 , ‘classmap’ => array( ‘Person’ => «Person» , ‘PersonList’ => «PersonList» ) ));
$PersonList =new PersonList ;
$client -> someMethod ( $PersonList );
?>
So every class, which will transfer via SOAP, must be extends from class SOAPable.
As you can see, in code above, function prepareSOAPrecursive search another nested objects in parent object or in arrays, and if does it, tries call function getAsSOAP() for preparation of nested objects, after that simply wrap up via SoapVar class.
So in code before transmitting simply call $obj->getAsSOAP()
If you are having an issue where SOAP cannot find the functions that are actually there if you view the wsdl file, it’s because PHP is caching the wsdl file (for a day at a time). To turn this off, have this line on every script that uses SOAP: ini_set(«soap.wsdl_cache_enabled», «0»); to disable the caching feature.
Juste a note to avoid wasting time on php-soap protocol and format support.
Until php 5.2.9 (at least) the soap extension is only capable of understanding wsdl 1.0 and 1.1 format.
The wsdl 2.0, a W3C recommendation since june 2007, ISN’T supported in php soap extension.
(the soap/php_sdl.c source code don’t handle wsdl2.0 format)
The wsdl 2.0 is juste the 1.2 version renamed because it has substantial differences from WSDL 1.1.
The differences between the two format may not be invisible if you don’t care a lot.
The typical error message if you provide a wsdl 2.0 format file :
PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn’t find in ‘wsdl/example.wsdl’ in /path/client.php on line 9
Was calling an asmx method like $success=$x->AuthenticateUser($userName,$password) and this was returning me an error.
However i changed it and added the userName and password in an array and its now KAWA.
If anyone is trying to use this for accessing Sabre’s web services, it won’t work. Sabre checks the request header «Content-Type» to see if it is «text/xml» . If it is not text/xml then it sends an error back.
You will need to create a socket connection and use that to send the request over.
Here is an example of a php client talking to a asmx server:
// Prepare SoapHeader parameters
$sh_param = array(
‘Username’ => ‘username’ ,
‘Password’ => ‘password’ );
$headers = new SoapHeader ( ‘http://soapserver.example.com/webservices’ , ‘UserCredentials’ , $sh_param );
// Prepare Soap Client
$soapClient -> __setSoapHeaders (array( $headers ));
// Setup the RemoteFunction parameters
$ap_param = array(
‘amount’ => $irow [ ‘total_price’ ]);
// Call RemoteFunction ()
$error = 0 ;
try <
$info = $soapClient -> __call ( «RemoteFunction» , array( $ap_param ));
> catch ( SoapFault $fault ) <
$error = 1 ;
print( »
alert(‘Sorry, blah returned the following ERROR: » . $fault -> faultcode . «-» . $fault -> faultstring . «. We will now take you back to our home page.’);
window.location = ‘main.php’;
» );
>
if ( $error == 0 ) <
$auth_num = $info -> RemoteFunctionResult ;
// Setup the OtherRemoteFunction() parameters
$at_param = array(
‘amount’ => $irow [ ‘total_price’ ],
‘description’ => $description );
// Call OtherRemoteFunction()
$trans = $soapClient -> __call ( «OtherRemoteFunction» , array( $at_param ));
$trans_result = $trans -> OtherRemoteFunctionResult ;
.
> else <
// Record the transaction error in the database
// Kill the link to Soap
unset( $soapClient );
>
>
>
>