GH-3734: Support MessageHistory on Kafka deser #3753
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 #3734
The
MessageHistory
is not in the trusted packages of theDefaultKafkaHeaderMapper
therefore it fails when
MessageHistory.read()
is performed.Configure default
DefaultKafkaHeaderMapper
in theSubscribableKafkaChannel
,KafkaInboundGateway
,KafkaMessageDrivenChannelAdapter
andKafkaMessageSource
to also trust packages exposed via
JacksonJsonUtils.DEFAULT_TRUSTED_PACKAGES
which include a
MessageHistory
, too.Verify in some integration Kafka tests to be sure that
MessageHistory
isdeserialized properly in the transferred headers
Rework some tests to use
@EmbeddedKafka
instead of@BeforeAll/@AfterAll
Cherry-pick to
5.5.x