I am still studying spring technology, so perhaps I don't understand this concept. However I think the resolution mechanism is more comparable with constructor mode autowiring than with constructor based dependency injection (argument matching)?
Comment From: pivotal-cla
@arnovh Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@arnovh Thank you for signing the Contributor License Agreement!
Comment From: sbrannen
Hi @arnovh,
Thanks for submitting your first PR!
However I think the resolution mechanism is more comparable with constructor mode autowiring than with constructor based dependency injection (argument matching)?
I can certainly understand why you would think that, since they are closely related concepts.
However, your proposed change would direct the user to autowiring modes that are only applicable when using Spring's XML configuration. Whereas, for an @Bean method the mechanism for autowiring by type for method parameters is effectively the same as for constructors and static factory methods.
In general, an @Bean method is a form of a factory method.
In light of the above, I am closing this PR.