调用SOAP Web服务时，SOAP请求的核心必备要素有哪些？

Got it, let's break down the non-negotiable elements you need when firing off a SOAP request—since you're already comfortable with REST's key-value pairs, this should feel familiar with a few SOAP-specific twists:

1. Target Endpoint URL #

Just like REST, you need the exact URL where the SOAP service lives. This is the destination you send your request to, e.g., https://your-service-domain.com/soap/inventory-management. No correct URL = no request reaching the service.

2. SOAP Envelope (The Mandatory XML Payload) #

SOAP is all about XML structure, and the Envelope is the root of every valid request. It must wrap two core parts (one mandatory, one sometimes required):

• <soap:Body>: Non-negotiable. This is where you put your actual business request data (like asking to fetch a user's order details).
• <soap:Header>: Optional in some cases, but mandatory if the service requires things like authentication tokens, session IDs, or custom metadata.

Here's a minimal valid example:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <FetchUserOrder>
      <UserID>9876</UserID>
      <OrderStatus>Shipped</OrderStatus>
    </FetchUserOrder>
  </soap:Body>
</soap:Envelope>

3. HTTP Request Method & Critical Headers #

SOAP sticks mostly to one HTTP method, plus a couple of non-negotiable headers:

• Request Method: 99% of the time, it's POST. Unlike REST, SOAP doesn't use GET/PUT/DELETE for different operations—all calls go via POST.
• Headers:
  • Content-Type: Must be set correctly. For SOAP 1.1, use text/xml; for SOAP 1.2, use application/soap+xml. Mess this up, and the service will reject your request outright.
  • SOAPAction: Required for SOAP 1.1. This is an HTTP header that tells the service which specific operation you're calling (e.g., "http://your-service-domain.com/FetchUserOrder"). SOAP 1.2 lets you skip this by adding an Action attribute to the Envelope, but many services still expect the header anyway.

4. Correct XML Namespace Declarations #

SOAP relies heavily on XML namespaces to avoid ambiguity between different service operations and data types. You must declare the correct namespaces in your Envelope and request elements (e.g., xmlns:ns="http://your-service-domain.com/inventory"). If the namespace is missing or incorrect, the service won't recognize the operation you're trying to call.

5. Payload Structure Matching the WSDL #

Every SOAP service defines its interface in a WSDL (Web Services Description Language) file. Your request's body elements must strictly match what's defined in the WSDL: correct field names, proper data types, and even element order matter. For example, if the WSDL says UserID must be an integer, sending a string will trigger a SOAP fault error.

内容的提问来源于stack exchange，提问作者RMD