Allow applications to specify a custom set of beans rather than the default for EventListener candidates [SPR-17343]

[spring-projects-issues]

Rahul Shinde opened SPR-17343 and commented

While benchmarking an application that has more than 10K+ beans, around 8 - 10 seconds was spent in identifying just the EventListener candidates during startup. 

Since we have the information for EventListener implementations beforehand, would like to provide that to avoid introspection of all other beans in the registry.

Applications can then extend EventListenerMethodProcessor and provide their own implementation that specifies subset of bean names to inspect.

 

---

Affects: 5.0.9, 5.1 GA

Referenced from: pull request #1980

[spring-projects-issues]

Stéphane Nicoll commented

Juergen Hoeller I wonder if the component index couldn't be extended to pre-compute that information. Rather than providing a hook point, we could redirect this project to use the index (10K is quite a lot)

[snicoll]

Duplicate of #1980