Class XmlJmsBrowserSender

  • All Implemented Interfaces:
    IConfigurable, IConfigurationAware, INamedObject, IScopeProvider, ISender, ISenderWithParameters, IWithParameters, org.springframework.beans.factory.Aware, org.springframework.context.ApplicationContextAware

    public class XmlJmsBrowserSender
    extends SenderWithParametersBase
    Sender for browsing and removing queue messages (with input and output in a XML message).

    When input root element is browse all queue messages are returned.

    When input root element is remove all queue messages are removed.

    example (input):


    example (browse output):

                <items count="2">
                      <timestamp>Thu Nov 20 13:36:31 CET 2014</timestamp>
                      <timestamp>Thu Dec 12 11:59:22 CET 2014</timestamp>

    example (remove output):


    Peter Leeuwenburgh
    • Constructor Detail

      • XmlJmsBrowserSender

        public XmlJmsBrowserSender()
    • Method Detail

      • createJmsBrowser

        public JmsBrowser<javax.jms.Message> createJmsBrowser()
      • sendMessage

        public SenderResult sendMessage​(Message message,
                                        PipeLineSession session)
                                 throws SenderException,
        Description copied from interface: ISender
        Send a message to some destination (as configured in the Sender object). This method may only be called after the configure() method is called.

        The following table shows the difference between synchronous and a-synchronous senders:

        ISender.isSynchronous() returnstruefalse
        return value of sendMessage() isthe reply-messagethe messageId of the message sent
        the correlationID specified with sendMessage()may be ignoredis sent with the message
        a {link TimeOutException}may be thrown if a timeout occurs waiting for a replyshould not be expected

        Multiple objects may try to call this method at the same time, from different threads. Implementations of this method should therefore be thread-safe, or synchronized.