-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Not able to set custom converters to MongoDbMessageStore #2936
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Well, that is really why we have introduced a We can't abuse internally a provided instance because that one can be used in any other place.
So, you should consider to add those The But as Gary said in the mentioned SO question, there is no reason to worry about a |
@artembilan But can't we add a hook to allow him to add his custom converter to the template? From the SO comments..
Seems like |
Yes, that we can do: add |
Agreed. |
Fixes spring-projects#2936 * Add `MongoDbMessageStore.setCustomConverters()` to allow to inject any custom converters for `payload` as well as header values **Cherry-pick to 5.1.x**
Fixes spring-projects#2936 * Add `MongoDbMessageStore.setCustomConverters()` to allow to inject any custom converters for `payload` as well as header values **Cherry-pick to 5.1.x**
Fixes #2936 * Add `MongoDbMessageStore.setCustomConverters()` to allow to inject any custom converters for `payload` as well as header values **Cherry-pick to 5.1.x**
Fixes #2936 * Add `MongoDbMessageStore.setCustomConverters()` to allow to inject any custom converters for `payload` as well as header values **Cherry-pick to 5.1.x**
Affects Version(s): <Spring Integration version>
spring-integration-mongodb
5.1.2.RELEASE
As explained in https://stackoverflow.com/questions/56215529/configurablemongodbmessagestore-failed-to-instantiate-org-springframework-messa#
there is a need to be able to add custom converters to MongoDbMessageStore or successfully inject ConfigurableMongoDbMessageStore with a MongDbTemplate containing custom converters.
Please assist.
The text was updated successfully, but these errors were encountered: