Detect default JmsListenerContainerFactory automatically [SPR-11706]

[spring-projects-issues]

Stéphane Nicoll opened SPR-11706 and commented

@JmsListener has a containerFactory attribute used to refer to the JmsListenerContainerFactory to use. The default can be set explicitly either using the XML namespace

<jms:annotation-driven default-container-factory="myFactory"/>

or using java config

@Configuration
@EnableJms
public class AppConfig implements JmsListenerConfigurer {

    @Override
    public void configureJmsListeners(JmsListenerEndpointRegistrar registrar) {
        registrar.setDefaultContainerFactory(myFactory());
    }
}

If that's specified, the containerFactory attribute can be omitted and the default will be assumed in that case.

A large majority of applications are using a single JMS broker and most are just using the sample template to create the container (different concurrency level may be what they would really need to change and topic/queue switch). We could decide to auto-detect the default container factory to use (and still give the ability to specify it explicitly of course!).

Proposal: lookup by name with "jmsListenerContainerFactory"

Also, look at <tx:annotation-driven> for reference

---

Affects: 4.1 RC1

Referenced from: commits 4b0aba6

[spring-projects-issues]

Stéphane Nicoll commented

Let's go with this and also remove the "default" prefix as it does not really mean what's intended here. Most applications would have only one factory so it's rather "the factory" with the ability to customize a different one per endpoint if needed.