WebServices: SOAP Message Structure
Envelope: Envelope is the root of the SOAP request. defines the XML document as a SOAP message and it contains the header and body element.
Header: Header contains auxiliary information, as SOAP blocks, such as authentication, routing information, or transaction identifier. The header is optional.
Body: Body contains the main information in one or more SOAP blocks. An example would be a SOAP block for RPC call. The body is mandatory and it must appear after the header.
Fault: Fault is a special block that indicates protocol-level errors. If present, it must appear in the body.
To Invoke a Web Service we should know the following things before going ahead.
1. The endpoint (target address) of the service
2. Exposed methods by the web service
3. Signature of the methods (Expected input-output parameters and types)
4. SOAP libraries which can serialize our invocation to a SOAP request and desterilize the SOAP response to desired return type.
Header: Header contains auxiliary information, as SOAP blocks, such as authentication, routing information, or transaction identifier. The header is optional.
Body: Body contains the main information in one or more SOAP blocks. An example would be a SOAP block for RPC call. The body is mandatory and it must appear after the header.
Fault: Fault is a special block that indicates protocol-level errors. If present, it must appear in the body.
To Invoke a Web Service we should know the following things before going ahead.
1. The endpoint (target address) of the service
2. Exposed methods by the web service
3. Signature of the methods (Expected input-output parameters and types)
4. SOAP libraries which can serialize our invocation to a SOAP request and desterilize the SOAP response to desired return type.
0 comments:
Post a Comment