Php soap ошибка

UPDATE July 2018

If you don’t care about getting the SoapFault details and just want to catch any errors coming from the SoapClient you can catch «Throwable» in PHP 7+. The original problem was that SoapClient can «Fatal Error» before it throws a SoapFault so by catching both errors and exceptions with Throwable you will have very simple error handling e.g.

try{
    soap connection...
}catch(Throwable $e){
    echo 'sorry... our service is down';
}

If you need to catch the SoapFault specifically, try the original answer which should allow you to suppress the fatal error that prevents the SoapFault being thrown

Original answer relevant for older PHP versions

SOAP can fatal error calling the native php functions internally which prevents the SoapFaults being thrown so we need to log and suppress those native errors.

First you need to turn on exceptions handling:

try {
    $client = new SoapClient("http://192.168.0.142:8080/services/Logon?wsdl",array(
       'exceptions' => true,
    ));
} catch ( SoapFault $e ) { // Do NOT try and catch "Exception" here
    echo 'sorry... our service is down';
}

AND THEN you also need to silently suppress any «PHP errors» that originate from SOAP using a custom error handler:

set_error_handler('handlePhpErrors');
function handlePhpErrors($errno, $errmsg, $filename, $linenum, $vars) {
    if (stristr($errmsg, "SoapClient::SoapClient")) {
         error_log($errmsg); // silently log error
         return; // skip error handling
    }
}

You will then find it now instead trips a SoapFault exception with the correct message «Soap error: SOAP-ERROR: Parsing WSDL: Couldn’t load from ‘…'» and so you end up back in your catch statement able to handle the error more effectively.

Вернуться к: SOAP Функции

Читаем wsdl. Находим нужный запрос.

<operation name="Tracking">
  <input message="tns:TrackingRequestMessage"/>
  <output message="tns:TrackingResponseMessage"/>
</operation>

Значит запрос Tracking принимает на вход TrackingRequestMessage. Смотрим дальше

<message name="TrackingRequestMessage">
  <part name="parameters" element="tns:Tracking"/>
</message>

Единственное поле parameters с типом Tracking. Ищем этот тип.

<xs:element name="Tracking">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="Language" type="xs:string" nillable="true"/>
      <xs:element name="Login" type="xs:string" nillable="true"/>
      <xs:element name="Password" type="xs:string" nillable="true"/>
      <xs:element name="Type" type="xs:string"/>
      <xs:element name="Documents" type="xs:string" nillable="true"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>

Получаем объект или ассоциативный массив с текстовыми полями Language, Login, Password, Type и Documents, причём все поля кроме Type могут иметь значение null.
Значит запрос должен выглядеть как

$result = $client->Tracking([
    'Language' => ?string,
    'Login' => ?string,
    'Password' => ?string,
    'Type' => string,
    'Documents' => ?string
]);

То же самое можно получить и средствами PHP. После подключения к клиенту получим список методов.

var_dump($client->__getFunctions());
/* ...
[92] => string(47) "TrackingResponse Tracking(Tracking $parameters)"
... */

Значит метод Tracking принимает один параметр с типом Tracking и возвращает ответ типа TrackingResponse.
Запросим типы.
var_dump($client->__getTypes());

/* ...
[120] => string(103) "struct Tracking {
 string Language;
 string Login;
 string Password;
 string Type;
 string Documents;
}"
[121] => string(51) "struct TrackingResponse {
 ResultTracking return;
}"
[24] => string(81) "struct ResultTracking {
 TrackingInfo Items;
 boolean Error;
 string ErrorInfo;
}"
[28] => string(227) "struct TrackingInfo {
 boolean Error;
 string Type;
 string Number;
 string Info;
 string AgentURL;
 dateTime CreateDate;
 string State;
 dateTime DeliveryDate;
 string DeliveryInfo;
 TrackingEvent History;
 Waybill Waybills;
}"
[27] => string(83) "struct TrackingEvent {
 dateTime EventDate;
 string EventName;
 string EventInfo;
}"
[31] => string(546) "struct Waybill {
 string Type;
 string Number;
 dateTime CreateDate;
 string State;
 dateTime DeliveryDate;
 string Sender;
 string SenderGeography;
 string Recipient;
 string RecipientGeography;
 string RecipientAddress;
 dateTime SendDate;
 string Payer;
 int CargoQty;
 float NetWeight;
 float GrossWeight;
 string ConsolidationNumber;
 string InventoryWaybillNumber;
 string DeliveryMethod;
 float Volume;
 boolean RequirePaymentInCash;
 float PaymentInCash;
 string PaymentInCashCurrency;
 string RecipientOfficial;
 TrackingEvent History;
}"
... */

Единственное отличие от самостоятельного анализа wsdl — не указано, какие поля необязательные, какие можно заполнять null и являются ли какие-то поля массивами.