Currently, the only way would be to configure the DefaultMessageListenerContainer bean and then provide that as a bean reference for the JmsGateway.
In theory, we could duplicate all of the configuration options of the message-listener container bean, but it doesn't seem right to do so. In fact, I am having second thoughts about doing as much as we are. It might be a lot simpler if we just expose a JMS MessageListener implementation (actually a Spring SessionAwareMessageListener) - including namespace support for that. Then, one could always use the core Spring "jms" namespace to do the following:
If the listener container configuration evolves, we would not be duplicating the effort, and besides, this would make it easier for someone to use other listener-container types.
<jms:listener-container ... >
<jms:listener ref="jmsInboundGateway" ... />
<si-jms:inbound-gateway id="jmsInboundGateway" ... />
Based on your current situation, would you actually agree that approach might be simpler?