From 06c16ae4525a65a5c56c77ce167372cc10df256b Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Wed, 20 Nov 2013 11:42:27 +0000 Subject: [PATCH] Only check for singleton in AutoConfigurationReportLoggingInitializer Using containsBean() involves looking in the parent bean factory if there is one, and that would mean that the same report woykd be used for multiple contexts, which wouldn't make sense. --- .../AutoConfigurationReportLoggingInitializer.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/AutoConfigurationReportLoggingInitializer.java b/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/AutoConfigurationReportLoggingInitializer.java index 31013fe97c..0a7f7cb146 100644 --- a/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/AutoConfigurationReportLoggingInitializer.java +++ b/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/AutoConfigurationReportLoggingInitializer.java @@ -59,7 +59,7 @@ public class AutoConfigurationReportLoggingInitializer implements public void initialize(ConfigurableApplicationContext applicationContext) { this.loggerBean = new AutoConfigurationReportLogger(applicationContext); ConfigurableListableBeanFactory beanFactory = applicationContext.getBeanFactory(); - if (!beanFactory.containsBean(LOGGER_BEAN)) { + if (!beanFactory.containsSingleton(LOGGER_BEAN)) { beanFactory.registerSingleton(LOGGER_BEAN, this.loggerBean); } }