donglao7947 2016-07-27 14:34
浏览 62


I have the SOAP endpoint and I would like to use PHP's \SoapClient class to send the request. The problem is that even if the "senderAddress" attribute has eg. "name", "nameDetail", "type" attributes (some of them are required by the docs), the generated XML request does not contain them. The only attribute it accepts/generates is the "id" attribute.

The same problem is also in another parts of the shipment object - f.ex. The Pickup part allows me to set just the "date" attribute, all of the others are skipped/ignored.

I've prepared some dummy code below, without data objects, just a simple array:

$soapClient = new \SoapClient("", [
    'trace' => 1
$headers = array();
$dpdSecurity = new \stdClass();
$token = new \stdClass();
$token->ClientKey = "topsecretkey";
$token->Email = "topsecretmail";
$dpdSecurity->SecurityToken = $token;
$headers["auth"] = new \SoapHeader('', 'DPDSecurity', $dpdSecurity);
$shipment = [
    "reference" => "123",
    "delisId" => "123",
    "addressSender" => [
        "type" => "b2c", // this attribute is missing in the Request
        "id" => 41656415651,
        "nameDetail" => "test", // this attribute is missing in the Request
    "addressRecipient" => "123",
    "product" => 9,
    "parcels" => [],
    "pickup" => null,
$params = [
    'shipment' => $shipment,
try {
    $response = $soapClient->CreateV1($params);
    echo '==' . PHP_EOL;
} catch (\Exception $e) {
    echo $e->getMessage();

Generated Request:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:ns1="" xmlns:ns2="">
            <ns1:pickup />
            <ns1:addressRecipient />
            <ns1:parcels />
  • 写回答

1条回答 默认 最新

  • doucang2871 2016-07-27 15:08

    The Shipment v1 schema states that the addressSender element is of type SHIPMENT:addressEnvelope, which is defined as such:

    <xsd:complexType name="addressEnvelope">
            <xsd:documentation>Address envelope</xsd:documentation>
                <xsd:element name="id" type="SHIPMENT:idType" minOccurs="0">
                        <xsd:documentation>Address ID</xsd:documentation>
                <xsd:element name="type" type="SHIPMENT:addresstypeType" minOccurs="0" />
                <xsd:element name="name" type="SHIPMENT:nameType" minOccurs="0">
                        <xsd:documentation>Contact person</xsd:documentation>
                <xsd:element name="nameDetail" type="SHIPMENT:nameType" minOccurs="0">
                        <xsd:documentation>Contact person (detail)</xsd:documentation>
                <xsd:element name="street" type="SHIPMENT:streetType" minOccurs="0" />
                <xsd:element name="streetDetail" type="SHIPMENT:streetType" minOccurs="0">
                        <xsd:documentation>Street (detail)</xsd:documentation>
                <xsd:element name="houseNumber" type="SHIPMENT:houseNumberType" minOccurs="0" />
                <xsd:element name="zip" type="SHIPMENT:zipType" minOccurs="0" />
                <xsd:element name="country" type="SHIPMENT:countryType" minOccurs="0" />
                <xsd:element name="city" type="SHIPMENT:cityType" minOccurs="0" />
                <xsd:element name="phone" type="SHIPMENT:phoneType" minOccurs="0" />
                <xsd:element name="email" type="SHIPMENT:emailType" minOccurs="0" />
                <xsd:element name="reference" type="SHIPMENT:referenceType" minOccurs="0">
                        <xsd:documentation>Reference for address (e.g. specific code of client)</xsd:documentation>
                <xsd:element name="note" type="SHIPMENT:noteType" minOccurs="0">
                        <xsd:documentation>Free note related to address</xsd:documentation>
                <xsd:element name="ico" type="SHIPMENT:icoType" minOccurs="0" />
                <xsd:element name="vatId" type="SHIPMENT:vatIdType" minOccurs="0" />
                <xsd:element name="vatId2" type="SHIPMENT:vatId2Type" minOccurs="0" />

    Since the addressEnvelope is a choice, you are only allowed to define one of the sequences. Since your data includes an id, the SoapClient uses the first sequence.

    Update Upon further testing, I can conclude that SoapClient will never choose the second sequence, since the first sequence only has an optional id element, which results in any data you provide being valid. The only way I was able to force SoapClient to choose the second sequence is by changing the minOccurs value of the id element to 1. To do this, you will have to download both the WSDL file and Shipment v1 schema, host them locally, and update the URLs.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?



  • ¥15 verilog modelsim仿真
  • ¥15 Power BI 里面 帕累托图突出显示前20
  • ¥50 用预估矫正法,分数阶微分方程组传染病的最优控制代码怎么写
  • ¥15 画个数据流程图,手画也行
  • ¥60 AS自带模拟器AVD Root 和 Xposed安装
  • ¥30 哪位搞Android的编程师可以帮我远程一下,悬赏30元
  • ¥15 solidity部署上合约,可以mint,也继承接口了,在区块链也不显示代币名字
  • ¥15 讨论 博士论文交互项怎么讨论?
  • ¥50 在集成BiLSTM和GCN模型时遇到了问题
  • ¥33 集成BiLSTM模型和GCN模型时,前模型的输出不匹配后模型的输入