Simple Object Access Protocol (SOAP) - Revision history

User at 21:07, 15 August 2023

2023-08-15T21:07:03Z

Show changes

User at 20:54, 15 August 2023

2023-08-15T20:54:01Z

User at 20:37, 15 August 2023

2023-08-15T20:37:40Z

User at 20:33, 15 August 2023

2023-08-15T20:33:51Z

Show changes

User at 00:10, 6 August 2023

2023-08-06T00:10:17Z

User at 21:40, 29 December 2022

2022-12-29T21:40:34Z

User at 16:07, 25 August 2022

2022-08-25T16:07:10Z

User at 16:06, 25 August 2022

2022-08-25T16:06:04Z

User at 15:36, 25 August 2022

2022-08-25T15:36:19Z

User at 15:26, 25 August 2022

2022-08-25T15:26:03Z

@@ Line 143: / Line 143: @@
 . Envelope
 The Envelope is the topmost element in a SOAP message. It defines the start and end of a message, making it clear what portions of the XML document are considered to be part of the SOAP message. It is a mandatory part of any SOAP message. The Envelope element encloses all other elements of the SOAP message.
 . Header
 The Header is an optional element used to contain application-specific information (like authentication, payment, etc.) or attributes of the message (like which web service action is being invoked). The Header element is used to add additional features and functionalities in the SOAP message. If specified, the Header is the first child element after the opening Envelope tag.
@@ Line 151: / Line 158: @@
 . Body
 The Body is a mandatory element and is used to contain the actual SOAP message intended for the ultimate endpoint of the message. It is the second child element after the opening Envelope tag. This is where the service request or response gets detailed.
 The Body element contains child elements, each representing a separate remote procedure call or a message. These elements are sometimes called SOAP body entries, and each one can encode the input or output parameters of a call.
@@ Line 156: / Line 167: @@
 . Fault
 The Fault element is an optional sub-element of the Body element. It is used to hold errors and status information for SOAP messages. If a Fault element is present, it must appear as a child of the Body element. This element is used to indicate error messages.
 faultcode: A code that categorizes the error. Standard fault codes are defined by the SOAP specification.
@@ Line 163: / Line 178: @@
 . Attachments (SOAP with Attachments)
 Though not a part of the core SOAP specification, SOAP messages can be used in combination with attachments. SOAP with Attachments is a specific way to associate documents of any type with a SOAP message. The attachments are not part of the actual SOAP message but are part of the extended SOAP message package, which includes the SOAP envelope and its associated attachments. Examples of this usage include sending an image, audio, or complex business data in formats like PDF or Word.
 Example of a Complete SOAP Message:
 Here is an example of what a complete SOAP message might look like:

@@ Line 151: / Line 151: @@
 . Body
 The Body is a mandatory element and is used to contain the actual SOAP message intended for the ultimate endpoint of the message. It is the second child element after the opening Envelope tag. This is where the service request or response gets detailed.
 ===See Also===

@@ Line 114: / Line 114: @@
 XML headers enclose the actual SOAP payloads. The XML element GetLastTradePriceResponse contains a response to the request for a trading price. The child element is Price, which indicates the value that is returned to the request.
 '''Advantages and Disadvantages of SOAP'''<ref>SOAP advantages and disadvantages [https://www.techtarget.com/searchapparchitecture/definition/SOAP-Simple-Object-Access-Protocol Techtarget]</ref><br />
@@ Line 150: / Line 122: @@
 *Platform- and operating system-independent. SOAP can be carried over a variety of protocols, enabling communication between applications with different programming languages on both Windows and Linux.
 *Works on the HTTP protocol. Even though SOAP works with many different protocols, HTTP is the default protocol used by web applications.
-*Can be transmitted through different network and security devices. SOAP can be easily passed through firewalls, where other protocols might require a special accommodation.
+*Can be transmitted through different networks and security devices. SOAP can be easily passed through firewalls, where other protocols might require a special accommodation.
 Disadvantages, however, include the following:

← Older revision		Revision as of 21:40, 29 December 2022
Line 1:		Line 1:
		+	== What is Simple Object Access Protocol (SOAP)? ==
		+
	'''SOAP (Simple Object Access Protocol)''' is the foundational, XML-based application protocol used to implement Web services within a SOA (Service Oriented Architecture). SOAP is transported primarily via HTTP and middleware messaging systems (JMS, MQ Series, MSMQ, Tuxedo, TIBCO RV) but can also be transported via other protocols such as SMTP (Simple Mail Transfer Protocol) and FTP (File Transfer Protocol).<ref>What is Simple Object Access Protocol (SOAP)? [https://www.f5.com/services/resources/glossary/simple-object-access-protocol-soap F5]</ref>		'''SOAP (Simple Object Access Protocol)''' is the foundational, XML-based application protocol used to implement Web services within a SOA (Service Oriented Architecture). SOAP is transported primarily via HTTP and middleware messaging systems (JMS, MQ Series, MSMQ, Tuxedo, TIBCO RV) but can also be transported via other protocols such as SMTP (Simple Mail Transfer Protocol) and FTP (File Transfer Protocol).<ref>What is Simple Object Access Protocol (SOAP)? [https://www.f5.com/services/resources/glossary/simple-object-access-protocol-soap F5]</ref>

← Older revision		Revision as of 16:07, 25 August 2022
Line 16:		Line 16:


−	'''History of SOAP'''<ref>History of SOAP [https://en.wikipedia.org/wiki/SOAP Wikipedia]</'ref>	+	'''History of SOAP'''<ref>History of SOAP [https://en.wikipedia.org/wiki/SOAP Wikipedia]</ref><br />
	SOAP was designed as an object-access protocol and released as XML-RPC in June 1998 as part of Frontier 5.1 by Dave Winer, Don Box, Bob Atkinson, and Mohsen Al-Ghosein for Microsoft, where Atkinson and Al-Ghosein were working. The specification was not made available until it was submitted to IETF 13 September 1999. According to Don Box, this was due to politics within Microsoft. Because of Microsoft's hesitation, Dave Winer shipped XML-RPC in 1998.		SOAP was designed as an object-access protocol and released as XML-RPC in June 1998 as part of Frontier 5.1 by Dave Winer, Don Box, Bob Atkinson, and Mohsen Al-Ghosein for Microsoft, where Atkinson and Al-Ghosein were working. The specification was not made available until it was submitted to IETF 13 September 1999. According to Don Box, this was due to politics within Microsoft. Because of Microsoft's hesitation, Dave Winer shipped XML-RPC in 1998.

@@ Line 14: / Line 14: @@
 *Encoding instructions for application defined data types.
 *Information about Remote Procedure Calls and their responses.<ref>Explaining SOAP [https://www.geeksforgeeks.org/basics-of-soap-simple-object-access-protocol/ Geeks for Geeks]</ref><br />
@@ Line 39: / Line 49: @@
 *Address of the service implementation (expressed as a URI)
 Using SOAP streamlines the process for exposing an existing software component as a Web service since the method signature of the service identifies the XML document structure used for both the request and the response.
@@ Line 109: / Line 139: @@
 #The client would format the information regarding the procedure call and any arguments into a SOAP message and sends it to the server as part of an HTTP request. This process of encapsulating the data into a SOAP message was known as Marshalling.
 #The server would then unwrap the message sent by the client, see what the client requested for and then send the appropriate response back to the client as a SOAP message. The practice of unwrapping a request sent by the client is known as Demarshalling.

@@ Line 82: / Line 82: @@
 XML headers enclose the actual SOAP payloads. The XML element GetLastTradePriceResponse contains a response to the request for a trading price. The child element is Price, which indicates the value that is returned to the request.
@@ Line 110: / Line 137: @@
 [[Service Oriented Architecture (SOA)]]<br />
 [[Enterprise Integration]]<br />
-[[Enterprise Architecture]]
+[[Enterprise Architecture]]<br />
 ===References===
 <references />

@@ Line 5: / Line 5: @@
 [[File:soap.png|400px|Simple Object Access Protocol (SOAP)]]<br />
-source: [https://msdn.microsoft.com/en-us/library/ms995800.aspx|MSDN]
+source: Microsoft
@@ Line 14: / Line 14: @@
 *Encoding instructions for application defined data types.
 *Information about Remote Procedure Calls and their responses.<ref>Explaining SOAP [https://www.geeksforgeeks.org/basics-of-soap-simple-object-access-protocol/ Geeks for Geeks]</ref><br />
 '''Points to Note About SOAP'''<ref>Points to Note About SOAP [https://www.tutorialspoint.com/soap/what_is_soap.htm TutorialsPoint]</ref><br />
@@ Line 38: / Line 39: @@
 *Address of the service implementation (expressed as a URI)
 Using SOAP streamlines the process for exposing an existing software component as a Web service since the method signature of the service identifies the XML document structure used for both the request and the response.