Ensure default TrackingEventProcessorConfiguration
is taken into account for Sagas
#2533
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.
The
EventProcessingConfigurer#registerTrackingEventProcessorConfiguration(Function<Configuration, TrackingEventProcessorConfiguration>)
did not overrule the default SagaTrackingEventProcessorConfiguration
.This is an unintended side effect when we introduced the default configuration for Sagas in issue #1019.
This pull request resolves that by adding the default
TrackingEventProcessorConfiguration
in the map ofTrackingEventProcessorConfigurations
whenEventProcessingConfigurer#registerTrackingEventProcessorConfiguration
is invoked.This provides a simple location to validate this customization when constructing the
TrackingEventProcessor
and when defining the Saga configuration.