Announcement Announcement Module
No announcement yet.
JMS Inbound Gateway (RC1) -- bug or config problem? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I appreciate that very much, and I appreciate your very quick response.

    But I need more than just making it resolve pubsubs,
    I need to connect to the pubsub using a durable subscription, currently there is no way to specify durable vs non durable subscriptions. I also need to specify the durableSubscriptionName, recoveryInterval, exceptionListener, cacheLevel. Neither one of those properties is exposed in the xml tag.

    Is there a problem with giving the option for specifying the MessageListenerContainer?

    I am using MQ version 6 as the jms provider.


    • #17
      No, that's not a problem, we should also enable setting the 'listener-container' reference.

      However, I'm also thinking that it almost seems easier to just provide the MessagePublishingListener so that you can use the "normal" Spring "jms" namespace.


      • #18
        Could you show an example of how it would look?

        How would I connect the Listener container to the si channel?


        • #19
          I am thinking of something like this:
          <jms:listener-container ... >
             <jms:listener ref="publisher"/>
          <bean id="publisher" class="...MessagePublishingListener">
             <property name="channel" ref="someChannel"/>
          In any case, providing the 'listener-container' reference would also work, and the JIRA issue has been scheduled for 1.0 Final.


          • #20
            That looks pretty straight forward, and it seems like it would be very simple to implement.

            Either way will work for me.

            Thank you so much for SI and for your excellent support.