Spring Boot Startup Failure: @Autowired vs @DubboReference Bean Injection Conflict

This article analyzes a Spring Boot startup failure caused by a conflict between @Autowired and @DubboReference annotations when injecting the same service bean. The problem occurs when a Spring bean (MvcInterceptorAutoConfiguration) requires an AccessContextService bean that is defined using @DubboReference in another class (ProxyCenter).

The core issue stems from the different injection mechanisms: @DubboReference uses a BeanPostProcessor (ReferenceAnnotationBeanPostProcessor) to create proxy objects and register them as singletons during property injection, while @Autowired attempts to resolve dependencies during bean creation. When @Autowired tries to inject AccessContextService before the @DubboReference proxy is registered, Spring fails to find the bean.

The article provides a detailed analysis of both annotation mechanisms, tracing through the Spring bean lifecycle and Dubbo's reference resolution process. It explains how @DubboReference creates ReferenceBean objects and registers them with the BeanFactory, but only after the owning bean is created.

The solution involves using a BeanFactoryPostProcessor to modify the bean definition of the problematic bean (accessContextResolver) to depend on the bean that contains the @DubboReference (proxyCenter), ensuring proper initialization order. The article also notes that this issue has been resolved in Dubbo 3.0.0 through improved initialization strategies.

Key takeaways include understanding the timing differences between annotation-based injection mechanisms and the importance of bean initialization order in complex dependency scenarios.