WARNING:
JavaScript is turned OFF. None of the links on this concept map will
work until it is reactivated.
If you need help turning JavaScript On, click here.
This Concept Map, created with IHMC CmapTools, has information related to: SOAP, Header Element that contains Header Information, <faultcode> could be one of the following Client, HTTP Request works like this, SOAP message contains the following elements Fault Element, Envelope Element defines the XML document as a SOAP message, <faultfactor> Information about who caused the fault, SOAP message must not contain a XML Processing Information, <detail> Holds application specific error information related to the Body Element, HTTP and XML is SOAP, SOAP Envelope Namespace should be like this xmlns:soap="http://www.w3.org/2001/12/soap-envelope", <faultcode> could be one of the following MustUnderstand, SOAP message must be encoded using XML, HTTP Client connects to the HTTP server using TCP, SOAP message must not contain a DTD reference, SOAP Encoding Namespace should be like this soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">, <faultcode> could be one of the following Server, SOAP contains a SOAP Method, encodingStyle is used to define the data types used in the XML document, actor looks like soap:actor="http://www.w3schools.com/appml/", HTTP Request for soap must complie with the SOAP Encoding Rules