Make WebServerFactoryCustomizerBeanPostProcessor registration GraalVM native compliant.
Closed this issue · 1 comments
As a follow-up of #146, depends on oracle/graal#2500.
After more work on that, context.registerBean("webServerFactoryCustomizerBeanPostProcessor", WebServerFactoryCustomizerBeanPostProcessor.class) does not work without reflection configuration due to oracle/graal#2500.
But we have an easy workaround since context.registerBean("webServerFactoryCustomizerBeanPostProcessor", WebServerFactoryCustomizerBeanPostProcessor.class, WebServerFactoryCustomizerBeanPostProcessor::new) works out of the box without any configuration.
It seems it was the only place where we did not use a lambda for calling the constructor.
Reflection entry for TomcatEmbeddedWebappClassLoader is also needed but that will be handled on spring-graalvm-native side.