Skip to content
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

Scanned components don't have the ability of being "primary" candidates [SPR-5155] #9828

Closed
spring-projects-issues opened this issue Sep 15, 2008 · 1 comment
Assignees
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Sep 15, 2008

Tuomas Kiviaho opened SPR-5155 and commented

Annotations don't have the possibility to flag a component as 'primary' candidate (nor can they be disabled from being 'autowire-candidate'). ScannedGenericBeanDefinition could quite easily be enhanced to support the feature if it's available in metadata.


Affects: 2.5.5

Issue Links:

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

We have an @Primary annotation as of 3.0 M3 now.

There is still no way to switch the autowire-candidate flag using an annotation... This shouldn't be necessary for scanned components, I would assume, in particular with the availability of @Primary now.

Juergen

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: core Issues in core modules (aop, beans, core, context, expression) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 M3 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants