You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When AutoConfigurationReproTests was introduced, it was testing some code in EmbeddedServletContainerAutoConfiguration that registered a EmbeddedServletContainerCustomizerBeanPostProcessor bean if one had not already been defined. That post-processor has now become WebServerFactoryCustomizerBeanPostProcessor that's registered by ReactiveWebServerFactoryAutoConfiguration or ServletWebServerFactoryAutoConfiguration.
The text was updated successfully, but these errors were encountered:
In fact, we can delete the class entirely as the post-processor and the potential for it to trigger early initialization is covered by WebServerFactoryCustomizerBeanPostProcessorTests.
wilkinsona
changed the title
Move AutoConfigurationReproTests nearer to the code that it's testing
Delete AutoConfigurationReproTests as testing for early init is covered by WebServerFactoryCustomizerBeanPostProcessorTests
Mar 4, 2025
When
AutoConfigurationReproTests
was introduced, it was testing some code inEmbeddedServletContainerAutoConfiguration
that registered aEmbeddedServletContainerCustomizerBeanPostProcessor
bean if one had not already been defined. That post-processor has now becomeWebServerFactoryCustomizerBeanPostProcessor
that's registered byReactiveWebServerFactoryAutoConfiguration
orServletWebServerFactoryAutoConfiguration
.The text was updated successfully, but these errors were encountered: