-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Reconsider PR #2769 #3130
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
This one is related: #3111 I don't have any immediate solution right now unless we will figure out some deep refactoring to resolve target message handlers much later in the endpoints, e.g. in their |
May I suggest
May that would be enough for us to just document in the Annotation section that beans which could be auto-wired from the messaging annotation processing should be marked with the |
Cool - I didn't realize you can use
Yes; I think this can be resolved with documentation, but we need to be clear it has to be on the |
Yep! Let's see what @membersound can say us about similar approach for beans method arguments injection! |
Fixes spring-projects#3111 Fixes spring-projects#3130 * Fix some typos in docs * Ensure in tests that announced `@Lazy` works as expected
* GH-3111: Document @lazy for messaging annotations Fixes #3111 Fixes #3130 * Fix some typos in docs * Ensure in tests that announced `@Lazy` works as expected * Doc Polishing Co-authored-by: Gary Russell <[email protected]>
#2769
Deferring the creation of integration components prevents injection:
I am sure that was not intended although the reason for the change is valid too.
Work around is to use a control bus:
The text was updated successfully, but these errors were encountered: