Remove MessageOriginProvider

Imported from Google Groups
1

I’m having to manually add a CorrelationDataProvider to my command handler configuration as it isn’t being configured automatically so I can define it as a bean. This results in there being two data providers registered, my manual one and the MessageOriginProvider.

The data I’m storing in meta data includes, amongst other things, a correlation ID which is generated by a Rails application before it reaches this service. The MessageOriginProvider includes a different correlationID in the metadata, so I would like to remove it to avoid any confusion.

Is it possible to expressly prevent the MessageOriginProvider by register when the command handler isn’t configured automatically?

Thanks

2

I’ve resolved this by adding the correlationDataProvider to the command Configuration builder, rather than adding it to the configuration after it’s been instantiated.