Please note that this documentation is currently under review!
Skip to end of metadata
Go to start of metadata

This section explains how the Messaging Mapper EIP can be implemented using WSO2 ESB. The following topics are covered:

Introduction to Messaging Mapper

The Messaging Mapper EIP moves data between domain objects and the messaging infrastructure, while keeping the two independent of each other. It contains the mapping logic between the messaging infrastructure and the domain objects. Neither the objects nor the infrastructure have knowledge of the Messaging Mapper's existence. For more information, refer to http://www.eaipatterns.com/MessagingMapper.html.

Figure 1: Messaging Mapper EIP

How WSO2 ESB implements the EIP

Messaging Mapper's objective is to serialize domain objects into a format more adaptable to the messaging infrastructure, such as SOAP or JSON.

In WSO2 ESB, the task of a Message Mapper is simulated by Message Builders and Message Formatters. They provide serialization logic to convert a byte stream to a standard data serialization format such as XML/SOAP or JSON. You can implement custom Message Builders/Formatters and plug them into the ESB to map just about any domain object into any sort of messaging infrastructure.

  • No labels