Since we are hijacking @ComponentScan to utilize @FrameworkControllerScan, this prevents a user from using it alongside any other @ComponentScan, including an @SpringBootApplication class.
Instead, a user is required to create a static inner class or @Import another @Configuration class that contains the @FrameworkControllerScan.
This represents work towards dynamically registering beans via an ImportBeanDefinitionRegistrar. Some work has already been done towards this effort at import-registrar. The challenge is that we need to build our own BeanDefinition from the class itself and don't have a lot of examples to rely on.
Since we are hijacking
@ComponentScanto utilize@FrameworkControllerScan, this prevents a user from using it alongside any other@ComponentScan, including an@SpringBootApplicationclass.Instead, a user is required to create a static inner class or
@Importanother@Configurationclass that contains the@FrameworkControllerScan.This represents work towards dynamically registering beans via an
ImportBeanDefinitionRegistrar. Some work has already been done towards this effort atimport-registrar. The challenge is that we need to build our ownBeanDefinitionfrom the class itself and don't have a lot of examples to rely on.