Introduction to Message
In an enterprise which uses Message Channels to connect between two different applications, the information is required to be packaged as a data set, which enables transmission of information from one application to the other. Message EIP is used as the transfer medium in this case. Message should comprise of two parts - a header which holds information describing the data being transmitted, its origin and its destination, and a Body which holds the data.
For more information on Message, refer to http://www.eaipatterns.com/Message.html.
Figure 1: Message EIP
How WSO2 ESB Supports Message EIP
As described in Messaging Bridge EIP, irrespective of the format a request is sent from the client application, WSO2 ESB transforms the message into a SOAP envelop, which adheres to the Message EIP. The following format illustrates the transformed message of a typical request. Notice that it has a header and a body.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://services.samples" xmlns:xsd="http://services.samples/xsd">
<soapenv:Header />
<soapenv:Body>
<ser:getQuote>
<ser:request>
<ser:symbol>FOO</ser:symbol>
</ser:request>
</ser:getQuote>
</soapenv:Body>
</soapenv:Envelope>