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
Introduce TypeFilterUtils for processing @ComponentScan.Filter #27553
Comments
Effectively what you want is the support provided by |
|
If we introduced something like |
Totally, it would also not require to make the component scan part public of ComponentScanAnnotationParser. |
ComponentScanAnnotationParser
@mp911de, please take a look at the new TypeFilterUtils and let us know if that meets your needs. |
Exactly what we need in Spring Data. Thank you. |
Spring Data leverages
ComponentScan.filter
for repository scanning while implementing the filter annotation parser itself.That arrangement has lead to differences in implementations such as the lack for
*Aware
callbacks (see spring-projects/spring-data-commons#2481). It would be good to be able to reuseComponentScanAnnotationParser
to ensure consistency for@Filter
support across projects leveragingComponentScan
-like functionality.The text was updated successfully, but these errors were encountered: