CorrelationDataInterceptor not auto-configured on Sagas #279

abuijze opened this Issue Feb 14, 2017 · 0 comments


None yet

1 participant

abuijze commented Feb 14, 2017

When using the Configuration API (or Spring) to register the Saga related components, the CorrelationDataProviders aren't used to attach correlation headers to any of the outgoing messages.

@abuijze abuijze added the Bug label Feb 14, 2017
@abuijze abuijze added this to the Release 3.0.3 milestone Feb 14, 2017
@abuijze abuijze added a commit that referenced this issue Feb 20, 2017
@abuijze abuijze SagaConfiguration now automatically defines CorrelationDataInterceptor
The CorrelationDataProviders registered with the Configurer will automatically be registered with this interceptor. This will complete the correlation data chain to all components capable of handling events.

Issue #279 Fixed
@abuijze abuijze assigned abuijze and unassigned abuijze Feb 20, 2017
@abuijze abuijze closed this Feb 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment