Spring5.0--你的PostConstruct注解为什么不生效

PostConstruct注解依靠CommonAnnotationBeanPostProcessor的父类InitDestroyAnnotationBeanPostProcessor执行,当你启动注解功能<context:annotation-config/>会自动帮你注册CommonAnnotationBeanPostProcessor。
当bean初始化的时候(对应方法AbstractAutowireCapableBeanFactory.initializeBean),会执行applyBeanPostProcessorsBeforeInitialization方法:所有注册的BeanPostProcessors的postProcessBeforeInitialization方法都会被执行(你的PostConstruct注解的执行就在这里面的InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization方法),除非被短路,spring4.0短路依靠执行结果是null则短路操作,spring5.0则有2个,一个是执行结果是null,一个是当前bean与执行结果相同,重点：ApplicationContextAwareProcessor这个类的源码会返回当前bean,所以你的PostConstruct注解一定会被短路而执行不到(如果你的PostConstruct放在BeanPostProcessors则不会被短路,会得到执行),这个不知道是不是spring的一个bug。
下面直接上spring5.0源码：
AbstractAutowireCapableBeanFactory.initializeBean方法源码：

protected Object initializeBean(String beanName, Object bean, @Nullable RootBeanDefinition mbd) {
       //如果bean实现了BeanFactoryAware等Aware接口则执行set那些方法
        if (System.getSecurityManager() != null) {
            AccessController.doPrivileged(() -> {
                this.invokeAwareMethods(beanName, bean);
                return null;
            }, this.getAccessControlContext());
        } else {
            this.invokeAwareMethods(beanName, bean);
        }
		//初始化之前方法,进入方法查看
        Object wrappedBean = bean;
        if (mbd == null || !mbd.isSynthetic()) {
            wrappedBean = this.applyBeanPostProcessorsBeforeInitialization(bean, beanName);
        }

		//依次执行初始化方法，如果实现了InitializingBean则执行afterPropertiesSet方法,如果配置了init-method执行该方法
        try {
            this.invokeInitMethods(beanName, wrappedBean, mbd);
        } catch (Throwable var6) {
            throw new BeanCreationException(mbd != null ? mbd.getResourceDescription() : null, beanName, "Invocation of init method failed", var6);
        }

		//执行初始化之后的方法
        if (mbd == null || !mbd.isSynthetic()) {
            wrappedBean = this.applyBeanPostProcessorsAfterInitialization(wrappedBean, beanName);
        }

        return wrappedBean;
    }

this.applyBeanPostProcessorsBeforeInitialization方法源码：

public Object applyBeanPostProcessorsBeforeInitialization(Object existingBean, String beanName) throws BeansException {
        Object result = existingBean;

        Object current;
        //获取所有注册的BeanPostProcessor,当执行postProcessBeforeInitialization的结果和当前bean相同则跳出执行
        //第一个执行的就是ApplicationContextAwareProcessor，立马就短路
        for(Iterator var4 = this.getBeanPostProcessors().iterator(); var4.hasNext(); result = current) {
            BeanPostProcessor processor = (BeanPostProcessor)var4.next();
            current = processor.postProcessBeforeInitialization(result, beanName);
            if (current == null) {
            //如果执行结果是null也跳出执行
                return result;
            }
        }
        return result;
    }

下面上ApplicationContextAwareProcessor.postProcessBeforeInitialization方法源码：

public Object postProcessBeforeInitialization(final Object bean, String beanName) throws BeansException {
		AccessControlContext acc = null;

		if (System.getSecurityManager() != null &&
				(bean instanceof EnvironmentAware || bean instanceof EmbeddedValueResolverAware ||
						bean instanceof ResourceLoaderAware || bean instanceof ApplicationEventPublisherAware ||
						bean instanceof MessageSourceAware || bean instanceof ApplicationContextAware)) {
			acc = this.applicationContext.getBeanFactory().getAccessControlContext();
		}

		if (acc != null) {
			AccessController.doPrivileged(new PrivilegedAction<Object>() {
				@Override
				public Object run() {
					invokeAwareInterfaces(bean);
					return null;
				}
			}, acc);
		}
		else {
		//就看这个方法
			invokeAwareInterfaces(bean);
		}
		//重点:返回了当前bean,结合上层判断,短路操作，你的PostConstruct注解对应的处理器InitDestroyAnnotationBeanPostProcessor已经被短路了
		return bean;
	}
//大体也是执行一些aware接口的set方法,并没有其他操作
private void invokeAwareInterfaces(Object bean) {
		if (bean instanceof Aware) {
			if (bean instanceof EnvironmentAware) {
				((EnvironmentAware) bean).setEnvironment(this.applicationContext.getEnvironment());
			}
			if (bean instanceof EmbeddedValueResolverAware) {
				((EmbeddedValueResolverAware) bean).setEmbeddedValueResolver(
						new EmbeddedValueResolver(this.applicationContext.getBeanFactory()));
			}
			if (bean instanceof ResourceLoaderAware) {
				((ResourceLoaderAware) bean).setResourceLoader(this.applicationContext);
			}
			if (bean instanceof ApplicationEventPublisherAware) {
				((ApplicationEventPublisherAware) bean).setApplicationEventPublisher(this.applicationContext);
			}
			if (bean instanceof MessageSourceAware) {
				((MessageSourceAware) bean).setMessageSource(this.applicationContext);
			}
			if (bean instanceof ApplicationContextAware) {
				((ApplicationContextAware) bean).setApplicationContext(this.applicationContext);
			}
		}
	}