With XML bridges, there are two stages that are used to identify received messages and determine what to do with those that are not expected. In order to know what's not expected, the Message Types section of the bridge allows the specification of message schemas. Any number of schemas can be configured under the Message Type Picker dialog box as shown in the following screenshot:

Message Types

The first stage in an XML bridge is Decode. This is only applicable for flat files, that is, messages that are not received as XML and have a flat file schema specified (more on flat file schemas in Chapter 4, Enterprise Application Integration). While processing flat files in an XML bridge may sound strange, the purpose of the bridge is to normalize the message into an XML format as this is what allows uniformity of processing useful features such as transformation and enrichment. In this way, data in any format, for example JSON, can be received and processed. There is nothing to configure...