Show Table of Contents
15.2.3. Gateway Data Mappings
When a non-ESB message is received by a gateway listener, it is converted into an ESB Message. How this is done depends upon the type of gateway listener involved. Here are the default approaches for each kind of gateway::
- JMS Gateway
- If the input message is a JMS TextMessage, then the associated String will be placed in the default named Body location. If it is an ObjectMessage or a BytesMessage then the contents are placed within the BytesBody.BYTES_LOCATION named "Body location".
- Local File Gateway
- This one places the contents within the BytesBody.BYTES_LOCATION named "Body location".
- Hibernate Gateway
- The contents are placed within the ListenerTagNames.HIBERNATE_OBJECT_DATA_TAG named "Body location".
- Remote File Gateway
- The contents are placed within the BytesBody.BYTES_LOCATION named "Body location".
Note
With the introduction of the InVM transport, it is now possible to deploy services within the same address space (VM) as a gateway, improving the efficiency of gateway-to-listener interactions.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.