-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HandlerMappingIntrospectorRequestTransformer
is registered twice in AOT
#14362
Comments
…stProcessor passive Instead of excluding the bean from AOT processing, we avoid redefining the beans if they are present or in the expected state. Issue gh-14362
@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. |
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. |
Unfortunately this doesn't work for me. |
Avoids GraalVM Native Image issues: spring-projects/spring-security#14362
Avoids GraalVM Native Image issues: spring-projects/spring-security#14362
Avoids GraalVM Native Image issues: spring-projects/spring-security#14362
The new changes added via #14128 introduced a
BeanDefinitionRegistryPostProcessor
that, among other things, register aHandlerMappingIntrospectorRequestTransformer
bean.The problem arises from the fact that the
BeanFactoryPostProcessor
s 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:
The text was updated successfully, but these errors were encountered: