GH-3052: Fix custom converters for lambdas #3053
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3052
Starting with version
5.1
, aLambdaMessageProcessor
is based on theMessageConverter
instead of plainConversionService
.(A
ConfigurableCompositeMessageConverter
is used from the applicationcontext.)
However a type conversion based on the
@IntegrationConverter
is lostin the
GenericMessageConverter
because it doesn't use anintegrationConversionService
from the application contextConfigurableCompositeMessageConverter
to configure aGenericMessageConverter
with anintegrationConversionService
if any
MessagingMethodInvokerHelper
to populate aBeanFactory
intoits internal
ConfigurableCompositeMessageConverter
LambdaMessageProcessorTests
that@IntegrationConverter
is applied for ``LambdaMessageProcessor` as wellCherry-pick to 5.1.x