GH-2708: Make messaging annotations as repeatable #3784
Conversation
Fixes spring-projects#2708 There are some requests to use the same service method for different input channels * Make all the messaging annotations as `@Repeatable` with their respective container annotations * Modify `MessagingAnnotationPostProcessor` logic to deal with the mentioned repeatable requirements
| ==== | ||
|
|
||
| You can also use the `@Headers` annotation to provide all of the message headers as a `Map`, as the following example shows: | ||
| You can also use the `@Headers` annotation to provide all the message headers as a `Map`, as the following example shows: |
There was a problem hiding this comment.
The English was correct.
| You can also use the `@Headers` annotation to provide all the message headers as a `Map`, as the following example shows: | |
| You can also use the `@Headers` annotation to provide all of the message headers as a `Map`, as the following example shows: |
There was a problem hiding this comment.
Cancel that: https://jakubmarian.com/is-it-all-the-or-all-of-the-in-english/
correct All the people I know were there.
correctAll of the people I know were there. (see below)
Having said that, the variant without “of” is significantly more common than the variant with “of”, to such a degree that the variant with “of” might be considered unnatural
There was a problem hiding this comment.
No problem, Gary.
Just followed IDEA suggestion:
And here is some article discussing such a matter: https://jakubmarian.com/is-it-all-the-or-all-of-the-in-english/
Do you have arguments against? 😄
Because I really sometimes blindly follow whatever my IDE suggests...
Thanks
2 participants
Fixes #2708
There are some requests to use the same service method for different input channels
@Repeatablewith theirrespective container annotations
MessagingAnnotationPostProcessorlogic to deal with the mentioned repeatablerequirements