Class MessageListenerAdapter

  • All Implemented Interfaces:
    MessageListener, SessionAwareMessageListener<Message>, SubscriptionNameProvider

    public class MessageListenerAdapter
    extends AbstractAdaptableMessageListener
    implements SubscriptionNameProvider
    Message listener adapter that delegates the handling of messages to target listener methods via reflection, with flexible message type conversion. Allows listener methods to operate on message content types, completely independent from the JMS API.

    By default, the content of incoming JMS messages gets extracted before being passed into the target listener method, to let the target method operate on message content types such as String or byte array instead of the raw Message. Message type conversion is delegated to a Spring JMS MessageConverter. By default, a SimpleMessageConverter will be used. (If you do not want such automatic message conversion taking place, then be sure to set the MessageConverter to null.)

    If a target listener method returns a non-null object (typically of a message content type such as String or byte array), it will get wrapped in a JMS Message and sent to the response destination (either the JMS "reply-to" destination or a specified default destination).

    Note: The sending of response messages is only available when using the SessionAwareMessageListener entry point (typically through a Spring message listener container). Usage as standard JMS MessageListener does not support the generation of response messages.

    Find below some examples of method signatures compliant with this adapter class. This first example handles all Message types and gets passed the contents of each Message type as an argument. No Message will be sent back as all of these methods return void.

    public interface MessageContentsDelegate {
        void handleMessage(String text);
        void handleMessage(Map map);
        void handleMessage(byte[] bytes);
        void handleMessage(Serializable obj);
    This next example handles all Message types and gets passed the actual (raw) Message as an argument. Again, no Message will be sent back as all of these methods return void.
    public interface RawMessageDelegate {
        void handleMessage(TextMessage message);
        void handleMessage(MapMessage message);
        void handleMessage(BytesMessage message);
        void handleMessage(ObjectMessage message);
    This next example illustrates a Message delegate that just consumes the String contents of TextMessages. Notice also how the name of the Message handling method is different from the original (this will have to be configured in the attandant bean definition). Again, no Message will be sent back as the method returns void.
    public interface TextMessageContentDelegate {
        void onMessage(String text);
    This final example illustrates a Message delegate that just consumes the String contents of TextMessages. Notice how the return type of this method is String: This will result in the configured MessageListenerAdapter sending a TextMessage in response.
    public interface ResponsiveTextMessageContentDelegate {
        String handleMessage(String text);
    For further examples and discussion please do refer to the Spring reference documentation which describes this class (and it's attendant XML configuration) in detail.
    Juergen Hoeller
    See Also:
    setDelegate(java.lang.Object), setDefaultListenerMethod(java.lang.String), AbstractAdaptableMessageListener.setDefaultResponseDestination(javax.jms.Destination), AbstractAdaptableMessageListener.setMessageConverter(, SimpleMessageConverter, SessionAwareMessageListener, AbstractMessageListenerContainer.setMessageListener(java.lang.Object)
    • Field Detail


        public static final java.lang.String ORIGINAL_DEFAULT_LISTENER_METHOD
        Out-of-the-box value for the default listener method: "handleMessage".
        See Also:
        Constant Field Values
    • Constructor Detail

      • MessageListenerAdapter

        public MessageListenerAdapter()
        Create a new MessageListenerAdapter with default settings.
      • MessageListenerAdapter

        public MessageListenerAdapter(java.lang.Object delegate)
        Create a new MessageListenerAdapter for the given delegate.
        delegate - the delegate object
    • Method Detail

      • setDelegate

        public void setDelegate(java.lang.Object delegate)
        Set a target object to delegate message listening to. Specified listener methods have to be present on this target object.

        If no explicit delegate object has been specified, listener methods are expected to present on this adapter instance, that is, on a custom subclass of this adapter, defining listener methods.

      • getDelegate

        protected java.lang.Object getDelegate()
        Return the target object to delegate message listening to.
      • getDefaultListenerMethod

        protected java.lang.String getDefaultListenerMethod()
        Return the name of the default listener method to delegate to.
      • getListenerMethodName

        protected java.lang.String getListenerMethodName(Message originalMessage,
                                                         java.lang.Object extractedMessage)
                                                  throws JMSException
        Determine the name of the listener method that is supposed to handle the given message.

        The default implementation simply returns the configured default listener method, if any.

        originalMessage - the JMS request message
        extractedMessage - the converted JMS request message, to be passed into the listener method as argument
        the name of the listener method (never null)
        JMSException - if thrown by JMS API methods
        See Also:
      • buildListenerArguments

        protected java.lang.Object[] buildListenerArguments(java.lang.Object extractedMessage)
        Build an array of arguments to be passed into the target listener method. Allows for multiple method arguments to be built from a single message object.

        The default implementation builds an array with the given message object as sole element. This means that the extracted message will always be passed into a single method argument, even if it is an array, with the target method having a corresponding single argument of the array's type declared.

        This can be overridden to treat special message content such as arrays differently, for example passing in each element of the message array as distinct method argument.

        extractedMessage - the content of the message
        the array of arguments to be passed into the listener method (each element of the array corresponding to a distinct method argument)