Red Hat Training

A Red Hat training course is available for JBoss Enterprise SOA Platform

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.