DEPRECATED: Processing a request-reply message with a Diffusion
client
A common pattern among JMS solutions is for a client to receive a message from JMS
and a reply is expected to be sent to a specific JMS topic or queue.
Note: The JMS Adapter v5.1 is now deprecated. Use the new JMS adapter instead. For more information, see JMS.
Typically, the JMS publisher creates and sends a message with the
JMSReplyTo header set to some other destination defined within
the JMS server. This can be a topic, queue, or a temporary topic or temporary queue.
The Diffusion™ client does not have to know the destination
type as this is handled within the adapter.
The Diffusion client subscribes to topic jms/queue/ABC.
The JMS provider creates a temporary queue, XYZ, and subscribes to it.
The JMS provider sends a message to the queue ABC with JMSReplyTo set to the queue XYZ.
The Diffusion client receives a message on queue
jms/topic/ABC, with
DiffusionReplyTo set to jms/reply/XYZ.
The Diffusion client sends a response message to the
queue jms/reply/XYZ.
The JMS provider receives a TextMessage on the temporary
queue XYZ. Figure 1. Request-reply initiated by a JMS client and serviced by a Diffusion client