Stéphane Nicoll opened SPR-14712 and commented

See #16509

The reason for our own scanning is that we need to find out whether we have to wire a custom repository implementation to the proxy or not. If we relied on the users declaring the implementation class as Spring bean, we can't be sure that bean definition is already available in the registry and thus we can't reliably decide whether to configure a runtime bean reference or not.
If the container provided means to create an optional bean reference by name, we could we could drop our own scanning.

Affects: 5.0 M1

Issue Links:

• Spring-specific index file for component candidate classes [SPR-11890] #16509 Spring-specific index file for component candidate classes