view release on metacpan or  search on metacpan

share/tnt-expressconnect/xsd/pricing/v3/PriceResponseOUT.xsd  view on Meta::CPAN

      <xs:element name="errorReason" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element contains a description indicating that the pricing request has failed and
            what
            action the customer should take.
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="errorSrcText" type="xs:string">
        <xs:annotation>
          <xs:documentation> This element might contain some additional information regarding the source of the
            error.
          </xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>

  <xs:complexType name="parseError">
    <xs:annotation>
      <xs:documentation>The XML parse error messages returned by
        ExpressConnect e.g. Element content is invalid
        according
        to the
        XSD/Schema.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="errorReason" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element contains a description indicating that the pricing request has failed and
            what
            action the customer should take.
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="errorLine" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element indicates the line number where the error occurred in the request XML.
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="errorLinepos" type="xs:string">
        <xs:annotation>
          <xs:documentation>This element indicates the position on the line where the error occurred in the request XML
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="errorSrcText" type="xs:string">
        <xs:annotation>
          <xs:documentation> This element might contain some additional information regarding the source of the
            error.
          </xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>

  <xs:complexType name="brokenRule">
    <xs:annotation>
      <xs:documentation>The brokenRule section is for application errors which the customer can resolve such as invalid
        postcode, login credentials.
      </xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="rateId" type="xs:string">
        <xs:annotation>
          <xs:documentation>The rateId is used to associate the error with the corresponding priceCheck.
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="messageType" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            This can be used to determine the severity of the error returned. The three categories are
            <xs:list>
              <xs:annotation>
                ‘I’ – Information
              </xs:annotation>
              <xs:annotation>
                ‘W’ – Warning
              </xs:annotation>
              <xs:annotation>
                ‘E’ - Error
              </xs:annotation>
            </xs:list>
          </xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="code" type="xs:string" />
      <xs:element name="description" type="xs:string" />
    </xs:sequence>
  </xs:complexType>


</xs:schema>