-
Notifications
You must be signed in to change notification settings - Fork 41.6k
Auto-configure BatchMessagingMessageConverter with Listener.Type.Batch #15708
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
Conversation
when use batch type listener, simple declare a bean of type RecordMessageConverter will not effect, should warp the RecordMessageConverter to a BatchMessagingMessageConverter when use batch type listener
@leochans Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@leochans Thank you for signing the Contributor License Agreement! |
paging @garyrussell |
@snicoll Functionally LGTM but there are code formatting violations. It also needs a couple of tests - one with, and one without a configured That said, I think a better solution would be to auto-configure a That would give the user more control over the converter, rather than hard-wiring a |
@garyrussell I had think about it's already init a |
I understand that (I wrote the code); it can be null without problems, but test cases are needed to ensure the configuration works as expected. However, I think my suggestion to auto-configure a |
Thank you for the PR @leochans but I've decided to take a different approach based on the feedback from @garyrussell, see #15942 for more details. |
when use batch type listener, simply declare a bean of RecordMessageConverter will not effect, should warp the RecordMessageConverter to a BatchMessagingMessageConverter when use batch type listener