Notify *Aware interfaces using custom type filters through Enable…Repositories#includeFilters

[f-cramer]

The javadoc for ComponentScan.Filter#classes specifies that custom instances of TypeFilter can implement any of 4 *Aware interfaces, whose methods should be called before matching.
When specifying a filter in EnableJpaRepositories#includeFilters, the methods of those interfaces are not called. Construtor autowiring cannot be used either, because filter instances are created using BeanUtils#instantiateClass(Class<?>).

[mp911de]

Thanks for bringing this up. Spring Data reuses ComponentScan filters but handles the parsing on its own. Spring Framework's ComponentScanAnnotationParser is not accessible and AnnotationRepositoryConfigurationSource.typeFiltersFor(…) follows a different implementation.

Support for *Aware callbacks was introduced at a later stage in Spring Framework and Spring Data never revised its filter handling.

Aligning with Spring Framework would help with consistency here.

[mp911de]

I moved this ticket into Spring Data Commons as the repository discovery is part of our common infrastructure.

[mp911de]

I filed spring-projects/spring-framework#27553 asking for reuse of Framework components for filter annotation parsing.

[mp911de]

Spring Framework provides now TypeFilterUtils that handle the creation of TypeFilter including *Aware callbacks.