Avoid hard logging of WebApplicationInitializer classes [SPR-14213]

[spring-projects-issues]

Phil Webb opened SPR-14213 and commented

SpringServletContainerInitializer currently finds, initializes and logs all WebApplicationInitializer implementations in onStartup. With Spring Boot this can be a little confusing because initializers might be conditional. We can't use the usual @Condition annotation since the ApplicationContext hasn't been created yet, but perhaps we could add a ConditionalWebApplicationInitializer extension to WebApplicationInitializer with an additional isActive() method.

See spring-projects/spring-boot#5778 for the original Boot bug.

---

Affects: 4.2.5, 4.3 RC1

Referenced from: commits 6a3d494, f73df2e

[spring-projects-issues]

Juergen Hoeller commented

I guess we could also consider other ways to avoid confusing log entries, e.g. to not log at that level at all...

[spring-projects-issues]

Juergen Hoeller commented

I've trimmed the log statement to just mention the number of initializers found, not listing the concrete classes.