Even if your messages are self-defining, and do not REQUIRE modeling, message modeling has the FOLLOWING advantages:

1. Runtime validation of messages. Without a message model, a parser cannot check whether input and output messages have the correct structure and data values.
2. Enhanced parsing of XML messages. Although XML is self-defining, all data values are treated as strings if a message model is not used. If a message model is used, the parser is provided with the data type of data values, and can cast the data accordingly.
3. Improved productivity when writing ESQL. When you are CREATING ESQL programs for WebSphere Message Broker message flows, the ESQL editor can USE message models to provide code completion assistance.
4. Drag-and-drop operations on message maps. When you are creating message maps for WebSphere Message Broker message flows, the Message Mapping editor uses the message model to populate its source and target views. Without message models, you cannot use the Message Mapping editor.
5. Reuse of message models, in whole or in part, by creating additional messages that are based on existing messages.
6. Generation of documentation.
7. PROVISION of version control and access control for message models by storing them in a central repository.

Even if your messages are self-defining, and do not require modeling, message modeling has the following advantages: