Browse Definitions :
Definition

SOAP fault

What is a SOAP fault?

A SOAP fault is an error in a Simple Object Access Protocol communication resulting from an incorrect message format, header-processing problems, incompatibility between applications or other issues.

SOAP facilitates communications between computers distributed across a network, even if they run on different operating platforms. SOAP is a highly structured, clearly defined architecture that can support an application programming interface.

Multiple standard protocols can carry SOAP messages, including the Hypertext Transfer Protocol, or HTTP; Simple Mail Transfer Protocol, or SMTP; and Transmission Control Protocol, or TCP.

A SOAP message is a specific type of Extensible Markup Language (XML) document that includes an <Envelope> element at the top level. The <Envelope> element must contain a <Body> element and can also contain an optional <Header> element.

The components of a SOAP message: envelope, header and body.
SOAP messages are XML documents that are composed of three basic building blocks. The fault message is an optional fourth building block.

When a SOAP fault occurs, a special type of SOAP message is generated that includes information about where the error originated and what caused it. The information is embedded in a <Fault> element, which itself is embedded in the document's <Body> element. The <Body> element can contain only one <Fault> element and cannot contain any other elements.

A SOAP message that contains a <Fault> element is known as a fault message. Here is an XML code snippet showing the basic structure of a SOAP fault message.

<env:Envelope xmlns:env=http://www.w3.org/2003/05/soap-envelope>
<env:Body>
<env:Fault>
<Fault subelements>
</env:Fault>
</env:Body>
</env:Envelope>

The URL in the opening <Envelope> tag points to the XML namespace for the more recent SOAP 1.2 specification, as opposed to SOAP 1.1. The structure is the same for both editions, which are actively used.

In this case, the <Fault> element includes the <Fault subelements> element. This is a placeholder for the various subelements, which provide the data about the specific fault. The subelements supported by the <Fault> element depend on whether you're working with SOAP 1.1 or SOAP 1.2.

SOAP 1.1 supports these subelements in the <Fault> element:

  • <faultcode> -- a mandatory element for identifying the type of fault. The SOAP standard defines a small set of type codes that can be specified in this element; however, they can be extended for specific applications.
  • <faultstring> -- a mandatory element for providing human-readable information about the nature of the fault.
  • <faultactor> -- an optional element for specifying the Uniform Resource Identifier (URI) of the SOAP node that was the source of the fault.
  • <detail> -- an optional element for providing application-specific error information. This element is required if the contents of the <Body> element cannot be otherwise processed.

The subelements changed in SOAP 1.2, although most share a similar purpose. SOAP 1.2 supports these subelements in the <Fault> element:

  • <Code> -- a mandatory element for identifying the type of fault. This element is similar to <faultcode> in SOAP 1.1, except it provides more extensive identification.
  • <Reason> -- a mandatory element for specifying human-readable information about the nature of the fault. This element is similar to <faultstring> in SOAP 1.1.
  • <Node> -- an optional element for providing the URI of the SOAP node that was the source of the fault. This element is similar to <faultactor> in SOAP 1.1.
  • <Role> -- an optional element for specifying the operational role of the SOAP node at the time of the fault.
  • <Detail> -- an optional element for providing application-specific error information. This element is similar to <detail> in SOAP 1.1.

Any node that participates in the SOAP communication can generate a fault message. If a node sends a SOAP request and an error is encountered, the receiving node transmits a fault message to the original node with information about the error. For example, a client might submit a request to a web server that relies on a particular service to carry out its functions. If the service is down, the server might return a SOAP fault message to the client with details about the error.

This was last updated in April 2023

Continue Reading About SOAP fault

Networking
  • subnet (subnetwork)

    A subnet, or subnetwork, is a segmented piece of a larger network. More specifically, subnets are a logical partition of an IP ...

  • Transmission Control Protocol (TCP)

    Transmission Control Protocol (TCP) is a standard protocol on the internet that ensures the reliable transmission of data between...

  • secure access service edge (SASE)

    Secure access service edge (SASE), pronounced sassy, is a cloud architecture model that bundles together network and cloud-native...

Security
  • cyber attack

    A cyber attack is any malicious attempt to gain unauthorized access to a computer, computing system or computer network with the ...

  • digital signature

    A digital signature is a mathematical technique used to validate the authenticity and integrity of a digital document, message or...

  • What is security information and event management (SIEM)?

    Security information and event management (SIEM) is an approach to security management that combines security information ...

CIO
  • product development (new product development)

    Product development -- also called new product management -- is a series of steps that includes the conceptualization, design, ...

  • innovation culture

    Innovation culture is the work environment that leaders cultivate to nurture unorthodox thinking and its application.

  • technology addiction

    Technology addiction is an impulse control disorder that involves the obsessive use of mobile devices, the internet or video ...

HRSoftware
  • organizational network analysis (ONA)

    Organizational network analysis (ONA) is a quantitative method for modeling and analyzing how communications, information, ...

  • HireVue

    HireVue is an enterprise video interviewing technology provider of a platform that lets recruiters and hiring managers screen ...

  • Human Resource Certification Institute (HRCI)

    Human Resource Certification Institute (HRCI) is a U.S.-based credentialing organization offering certifications to HR ...

Customer Experience
  • contact center agent (call center agent)

    A contact center agent is a person who handles incoming or outgoing customer communications for an organization.

  • contact center management

    Contact center management is the process of overseeing contact center operations with the goal of providing an outstanding ...

  • digital marketing

    Digital marketing is the promotion and marketing of goods and services to consumers through digital channels and electronic ...

Close