Default event-based item readers to bean name and remove strict name assertions #5153
+71
−138
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…assertions Added BeanNameAware to event item readers to use the bean name when no explicit name is provided. Removed name assertions from the corresponding builders. Closes: spring-projectsgh-5149 Signed-off-by: Andrey Litvitski <andrey1010102008@gmail.com>
Contributor
Author
|
Can you tell me roughly why this problem occurs? |
Contributor
It's a flaky test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added
BeanNameAwareto event item readers to use the bean name when no explicit name is provided. Removed name assertions from the corresponding builders.I've added a
BeanNameAwareimplementation wherever the builders have a name. I believe this is what was meant in #5149. In any case, we can look into it.Closes: #5149