`HandlerMappingIntrospectorRequestTransformer` is registered twice in AOT

[marcusdacoregio]

The new changes added via #14128 introduced a BeanDefinitionRegistryPostProcessor that, among other things, register a HandlerMappingIntrospectorRequestTransformer bean.

The problem arises from the fact that the BeanFactoryPostProcessors are invoked during AOT processing and once more at runtime, leading to a duplicate bean exception.

Usually org.springframework.beans.factory.config.BeanFactoryPostProcessor beans are excluded since they have contributed their bean definitions code generated during AOT build phase.

Related:

• AOT registers BeanDefinitionRegistryPostProcessor beans causing duplication of configuration spring-framework#30411
• Consider allowing to exclude some beans from AOT processed applications spring-framework#29484

[mraible]

@marcusdacoregio Do you know if this fix will be included in a release of Spring Boot before January 16? I'm trying to decide if I should use Spring Boot 3.2.0 or wait for 3.2.2 for a presentation I'm doing on that date.

[marcusdacoregio]

Hi, @mraible. Unfortunately no, this will be included in the next patch releases that will occur on February 19th and will probably be picked up by Spring Boot 3.2.3 in February 21st. An alternative is to use Spring Boot 3.2.2 and override the Spring Security version to use a SNAPSHOT.