Allow arbitrary packages to be scanned for Reflective usage #33132
Assignees
Labels
Milestone
Comments
snicoll
added
type: enhancement
|
As part of fixing this, we should make sure to review the javadoc of the existing annotation as well as the reference guide to provide examples to users. |
snicoll
added a commit
to snicoll/spring-framework
that referenced
this issue
Jul 6, 2024
This commit allows `@Reflective` to be used on arbitrary types, not only Spring beans. This makes the feature much more powerful as components can be tagged directly. Scanning happens during AOT processing (typically at build-time) when `@ReflectiveScan` is used. Types do not need to have a particular annotation, and types that can't be loaded are ignored. This commit also exposes the infrastructure that does the scanning so that custom code can do the scanning in an AOT contribution if they don't want to rely on the annotation. Closes spring-projectsgh-33132
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow-up of #29194
We'd like to make sure that non beans can define
@Reflectiveusage (or any composed annotations using it), so that any type can provide that information. It's a bit unclear how we can integrate such scanning. I don't know if we should go as far as introducing a@ReflectiveScanthat behaves the same way as@ComponentScanbut for reflective usage.I already have a working implementation that needs to be called explicitly with the packages to scan, see snicoll@24dc359.
Whether or not we want to introduce
@ReflectiveScanis largely dependent on how Spring Boot would like to integrate this feature. Ping @wilkinsona for feedback.The text was updated successfully, but these errors were encountered: