MethodJmsListenerEndpoint does not set the DestinationResolver on the MessagingMessageListenerAdapter [SPR-12927]

[spring-projects-issues]

Stephan Oudmaijer opened SPR-12927 and commented

The MethodJmsListenerEndpoint does not set a destination resolver in the createMessageListener() method. Therefore it always uses the DynamicDestinationResolver defined at spring-jms-4.1.6.RELEASE-sources.jar!/org/springframework/jms/listener/adapter/AbstractAdaptableMessageListener.java:60

---

Affects: 4.1.6

Issue Links:

• MessagingMessageListenerAdapter should use DestinationResolver of MessageListenerContainer [SPR-13059] #17651 MessagingMessageListenerAdapter should use DestinationResolver of MessageListenerContainer ("is duplicated by")

Referenced from: commits bd05e3a, 444b903

[spring-projects-issues]

Stéphane Nicoll commented

This is fixed and only for the @JmsListener infrastructure. The XML-based config had the same problem (probably since the beginning) and I guess that users have created a custom message listener adapter solution in this case. I am not too keen to change the default at this point.

[spring-projects-issues]

Juergen Hoeller commented

Marking this for 4.1.7 as well, as per the discussion on #17651.

[spring-projects-issues]

Stéphane Nicoll commented

This has been backported to 4.1