Messages that pass across this transport have an XML format that provides platform-independence. The XML content that defines specific operations, and error situations (SOAP Fault), is defined by the SOAP standard. Because delivery is not guaranteed, applications must provide recovery in the event of system or network failures.
A message contains components that are appropriate to its type:
In most cases, the body of a message is XML. However, an inbound message can contain a different format if the receiving node is configured to handle that format and the appropriate parsers are available. An outbound message can contain a body of any format that is accepted by the Web service to which it is sent.
An error that is generated by a component other than a Web service (for example, 404 Not Found) might result in a message that is in HTML format.
The bit stream containing headers and body are parsed and represented within the message tree when an input request is received by an HTTPInput node, or when a response from a Web service is received by the HTTPRequest node. A bit stream is created by parsers from the appropriate parts of the message tree when a reply is sent to the client by the HTTPReply node, and when a request is sent to a Web service by the HTTPRequest node. For further details about these actions, see the individual node descriptions.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac00476_ |