Consumer endpoints play the role of consumer from the vantage point of the other endpoints in the ESB. As shown in Figure 1,consumer endpoints listen for messages on a JMS destination. When the message is received, the consumer endpoint passes it onto the NMR for delivery. If the JMS message is part of an in-out message exchange, the consumer endpoint will place that message into a reply destination for delivery to the originator of the JMS message.
The JMS binding component offers three types of consumer endpoints:
- Generic
The generic consumer endpoint can handle any type of message data. It is configured using the
jms:consumerelement.- SOAP
The SOAP consumer endpoint is specifically tailored to receive SOAP messages. It uses a WSDL document to define the structure of the messages. It is configured using the
jms:soap-consumerelement.![[Tip]](imagesdb/tip.gif)
Tip The Apache CXF binding component's JMS transport is better adapted to handling SOAP messages, but offers less control over the JMS connection.
- JCA
The JCA consumer endpoint uses JCA to connect to the JMS provider. It is configured using the
jms:jca-consumerelement. For more information on using the JCA consumer endpoint, see Using the JCA Consumer Endpoint.
 |  |  |
 |
