Spring internal configuration classes can no longer use @EventListener [SPR-17160]

[spring-projects-issues]

Stéphane Nicoll opened SPR-17160 and commented

Due to this optimization, Spring projects can no longer use @EventListener.

Spring Boot does use it in a few places where a single component needs to listener for two event types and avoid being called for every event. We can move to ApplicationListener if necessary but it would be nice to have a strategy to narrow down the event types.

---

Affects: 5.1 RC2

Issue Links:

• Avoid unnecessary synthesizable annotation processing [SPR-16933] #21472 Avoid unnecessary synthesizable annotation processing
• Revisit @Bean introspection between @Configuration classes and 'lite' beans [SPR-17206] #21739 Revisit @Bean introspection between @Configuration classes and 'lite' beans

Referenced from: commits 1d59e52

[spring-projects-issues]

Stéphane Nicoll commented

For the record, Spring Boot master no longer uses @EventListener. 

[spring-projects-issues]

Juergen Hoeller commented

It seems that we can proceed with the original change for the time being. We may still re-evaluate towards GA.

[spring-projects-issues]

Juergen Hoeller commented

As reported by John Blum via email, we missed one case: the user class traversal for the generated configuration subclasses. This has been fixed for RC3 now.