You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit introduces automatic configuration of the `messageConverter` property for both the `JmsTemplate` and `DefaultJmsListenerContainerFactory`.
When a `MessageConverter` is configured it will be used to configure both classes.
Fixes: spring-projectsgh-4282
If a `MessageConverter` bean is available, we now associate it to the
created `JmsTemplate` and `JmsListenerContainerFactory`. That way,
registering a custom `MessageConverter` is all that's needed.
The JMS auto-configuration is now using the new `ObjectProvider` that
offers a nicer API to detect if a primary candidate is available for
optional collaborators.
Closesspring-projectsgh-4282
Currently when a
DestinationResolver
is found in the context it is automatically registered on theJmsTemplate
andDefaultJmsListenerContainerFactory
.It would be nice if this could also be the case for a
MessageConverter
.The text was updated successfully, but these errors were encountered: