JMS Inbound Gateway (RC1) -- bug or config problem?

[Mark Fisher]

The URL is: http://jira.springframework.org/browse/INT-482

As far as the pubsub configuration, the 'request-destination' can be any JMS Destination reference (Queue or Topic). Have you tried setting that for a Topic?

[paulpach]

To the best of my knowledge, and by looking at the code, it will only try to resolve Topics if isPubSubDomain is set.

so I am not sure what to put in request-destination to make it look for a topic without specifying isPubSubDomain.

But even if I do, I still need to make it a durable subscription and use some of the other advanced parameters in DefaultMessageListenerContainer.

[Mark Fisher]

If you are providing a Destination reference, it does not need the 'pubSubDomain' value. That is only necessary when it is resolving a destination-name.

However, it is true that we need to enable setting that boolean value alongside destination-name to ensure that Topics can be used when resolving by name.

[paulpach]

My destinations are by name, I do not have Destination objects set up in JNDI, so I am relying on DynamicDestinationResolver.

[Mark Fisher]

OK. I will be sure to include the addition of 'pub-sub-channel' when tackling the issue. Out of curiosity, what JMS provider are you using?

[paulpach]

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.

[Mark Fisher]

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.

[paulpach]

Could you show an example of how it would look?

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

[Mark Fisher]

I am thinking of something like this:

<jms:listener-container ... >
   <jms:listener ref="publisher"/>
</jms:listener-container>

<bean id="publisher" class="...MessagePublishingListener">
   <property name="channel" ref="someChannel"/>
</bean>

In any case, providing the 'listener-container' reference would also work, and the JIRA issue has been scheduled for 1.0 Final.

[paulpach]

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.