使用Java Config时如何防止Spring生命周期方法？

@Configuration
class MyConfig {
    @Bean
    public Problematicservice problematicservice() {
        Problematicservice service = someMethodOutsideMyControl();
        // Problematicservice is constructed for me by other code (outside of Spring)
        // and it happens to have a @postconstruct method. The @postconstruct method
        // cAnnot be invoked here or by Spring once this method returns.
        return service;
    }
}

这是一个非平凡的变化. @Configuration类(或者更确切地说是AnnotationConfigApplicationContext)注册一个CommonAnnotationBeanPostProcessor,它负责调用bean的@postconstruct方法.改变这意味着几乎改变整个Spring IoC堆栈.

实际上,您可以使用bean名称org.springframework.context.Annotation.internalCommonAnnotationProcessor声明CommonAnnotationBeanPostProcessor,它将覆盖默认名称.您可以将init注释类型设置为null,以便它忽略@postconstruct.

@Bean(name = "org.springframework.context.Annotation.internalCommonAnnotationProcessor")
public CommonAnnotationBeanPostProcessor commonAnnotationBeanPostProcessor() {
    CommonAnnotationBeanPostProcessor bean = new CommonAnnotationBeanPostProcessor();
    bean.seTinitAnnotationType(null);;
    return bean;
}

使用它时要小心,否则可能会破坏其他东西.

我将首先建议尝试找到解决方法.例如,返回一个包装器对象,它可以让您访问Problematicservice.

@Bean
public serviceProvider provider() {
    Problematicservice service = ...;
    serviceProvider provider = new serviceProvider(servicE);
    return provider;
}

或者类似你建议的factorybean.

另一个更酷但更丑陋的方法是将对象包装在cglib代理中.

@Bean
public Problematicservice service() {
    Problematicservice service = ...;
    Enhancer enhancer = new Enhancer();
    enhancer.setSuperclass(service.getClass());
    enhancer.setCallBACk(new MethodInterceptor() {
        Problematicservice inner = service;
        @Override
        public Object intercept(Object obj,Method method,Object[] args,MethodProxy proxy) throws Throwable {
            if (!method.getName().equals("initMethodName"))
                return method.invoke(inner,args);
            return null;
        }
    });
    return (ProblematicservicE) enhancer.create();
}

基本上,永远不能调用init方法.