XBUSXMLMessage represents messages in the xBus specific XML-format. It is very useful when a message leaves the context of the xBus and reenters again, e.g. it is buffered in a message queue or send to another instance of the xBus via HTTP.

01 <?xml version="1.0" encoding="UTF-8"?>
02 <XBUS_Document>
03     <XBUS_Call>
04         <Id>Example3InFile_1081273849920</Id>
05         <Function>Default</Function>
06         <Source>Example3HTTPSample1</Source>
07         <Address/>
08         <Timestamp>2004-04-06 19:50:50,200</Timestamp>
09     </XBUS_Call>
10     <XBUS_Data>
11         <![CDATA[<?xml version="1.0" encoding="UTF-8"?>
12                  <NameList>
13                      <Person>John Doe</Person>
14                      <Person>Mary Powers</Person>
15                  </NameList>
16         ]]>
17     </XBUS_Data>
18 </XBUS_Document>
02 - 09:
The first part (XBUS_Call) contains the header fields common to all message types. They are explained here.
10 - 17:
The second part (XBUS_Data) contains either the request or the response data of the message.
11 - 16:
In this example, the response data is a wrapped XML document. The XMLWrapperTransformer wraps arbitrary string messages into a XBUSXMLMessage by packing them into a CDATA section, to avoid the interpretation of the data by the XML parser.