1. FactoryBean的本质与设计初衷FactoryBean是Spring框架中一个特殊的接口它的存在打破了传统Bean实例化的单一模式。与普通Bean直接由Spring容器通过反射实例化不同FactoryBean本质上是一个能生产对象的工厂。这种设计源于两个核心需求第一当Bean的实例化过程过于复杂时传统的XML或注解配置方式会变得臃肿且难以维护。比如MyBatis的SqlSessionFactory需要配置数据源、mapper文件位置、类型别名等多达十余项参数。通过实现FactoryBean接口可以用Java代码灵活控制实例化逻辑将复杂配置封装在工厂内部。第二第三方库的集成往往需要特殊处理。以Dubbo的ReferenceBean为例它需要处理服务发现、负载均衡、集群容错等分布式逻辑这些无法通过简单配置实现。FactoryBean提供了接入这些外部系统的标准方式。关键理解FactoryBean是Spring对工厂方法模式的实现它的核心价值在于将对象创建过程从容器转移到自定义逻辑中。2. 核心方法与运行机制解析2.1 三方法契约详解FactoryBean接口定义的三个方法构成了完整的工厂协议public interface FactoryBeanT { T getObject() throws Exception; // 生产目标对象 Class? getObjectType(); // 声明产品类型 default boolean isSingleton() { // 控制产品作用域 return true; } }getObject()是核心生产方法其实现需要注意每次调用可能返回新实例视isSingleton返回值而定允许返回null需用Nullable标注可以抛出检查异常getObjectType()的特殊性常被误解Component public class MyFactory implements FactoryBeanFoo { Override public Class? getObjectType() { return Bar.class; // 实际返回类型可与泛型参数不同 } }这里虽然泛型声明为Foo但通过getObjectType()声明实际生产的是Bar类型。Spring容器会以此方法返回值作为类型匹配依据。2.2 命名访问的特殊规则FactoryBean在容器中的访问遵循特殊命名约定getBean(myFactory)返回工厂产品getBean(myFactory)返回工厂本身这种设计带来一个典型陷阱Autowired private MyFactory myFactory; // 注入的实际上是产品对象 Autowired private FactoryBeanFoo myFactory; // 这样才会注入工厂3. 典型应用场景深度剖析3.1 AOP代理创建机制Spring AOP的核心实现ProxyFactoryBean是FactoryBean的经典应用public class ProxyFactoryBean extends ProxyCreatorSupport implements FactoryBeanObject, BeanClassLoaderAware { public Object getObject() { return getProxy(); // 动态生成代理对象 } }其配置示例bean iduserServiceProxy classorg.springframework.aop.framework.ProxyFactoryBean property nametarget refuserService/ property nameinterceptorNames list valueloggingInterceptor/value /list /property /bean3.2 MyBatis集成实现SqlSessionFactoryBean展示了如何封装复杂初始化逻辑public class SqlSessionFactoryBean implements FactoryBeanSqlSessionFactory, InitializingBean { private DataSource dataSource; private String mapperLocations; public SqlSessionFactory getObject() throws Exception { SqlSessionFactoryBuilder builder new SqlSessionFactoryBuilder(); return builder.build(createSqlSessionFactoryConfiguration()); } private Configuration createSqlSessionFactoryConfiguration() { // 构建包含数据源、缓存等复杂配置的Configuration对象 } }3.3 动态策略模式实现通过FactoryBean可以实现运行时策略切换public class StrategyFactoryBean implements FactoryBeanProcessor { Value(${system.strategy}) private String strategyName; public Processor getObject() { switch(strategyName) { case A: return new FastProcessor(); case B: return new SafeProcessor(); default: throw new IllegalArgumentException(); } } }4. 高级应用与性能优化4.1 延迟初始化模式结合SmartFactoryBean实现智能初始化控制public class LazyFactoryBean implements SmartFactoryBeanExpensiveObject { public boolean isEagerInit() { return false; // 延迟到首次请求时初始化 } public ExpensiveObject getObject() { return new ExpensiveObject(loadHeavyResources()); } }4.2 对象池实现通过FactoryBean管理对象池public class PooledFactoryBean implements FactoryBeanConnection, DisposableBean { private final BlockingQueueConnection pool new LinkedBlockingQueue(10); public Connection getObject() throws InterruptedException { return pool.take(); // 从池中获取 } public void returnObject(Connection conn) { pool.offer(conn); // 返回到池中 } }4.3 缓存优化策略public class CachedFactoryBean implements FactoryBeanReportGenerator { private volatile ReportGenerator cachedInstance; public synchronized ReportGenerator getObject() { if (cachedInstance null) { cachedInstance createNewInstance(); } return cachedInstance; } private ReportGenerator createNewInstance() { // 执行耗时的初始化操作 } }5. 常见问题排查指南5.1 循环依赖问题当FactoryBean与其他Bean存在循环依赖时需要特别注意Component public class ServiceA { Autowired private ProductB productB; // 依赖FactoryBean生产的产品 } Component public class FactoryB implements FactoryBeanProductB { Autowired private ServiceA serviceA; // 与ServiceA形成循环 public ProductB getObject() { return new ProductB(serviceA); } }解决方案使用Lazy延迟注入通过Setter方法而非字段注入实现SmartFactoryBean的isEagerInit()返回false5.2 类型匹配异常典型错误场景Configuration public class Config { Bean public FactoryBeanCharSequence stringFactory() { return new StringFactoryBean(); } } Autowired private String text; // 注入失败容器中实际是CharSequence类型解决方法在getObjectType()中精确声明返回类型使用具体类型而非接口进行注入5.3 作用域失效问题当isSingleton()返回false时需注意public class PrototypeFactory implements FactoryBeanThread { public boolean isSingleton() { return false; } public Thread getObject() { return new Thread(); } } Autowired private Thread thread1; Autowired private Thread thread2; // thread1和thread2实际上是同一个实例原因Spring对FactoryBean产品的处理有特殊逻辑解决方案使用ObjectProvider延迟获取通过方法注入而非字段注入6. 源码级实现原理6.1 容器集成流程在AbstractBeanFactory中处理FactoryBean的核心逻辑protected Object getObjectForBeanInstance( Object beanInstance, String name, String beanName, RootBeanDefinition mbd) { // 处理前缀请求 if (BeanFactoryUtils.isFactoryDereference(name)) { return beanInstance; } // 处理普通FactoryBean产品请求 if (beanInstance instanceof FactoryBean) { return getObjectFromFactoryBean((FactoryBean?) beanInstance, name, beanName); } return beanInstance; }6.2 产品对象缓存机制FactoryBeanRegistrySupport中的关键实现private final MapString, Object factoryBeanObjectCache new ConcurrentHashMap(); protected Object getObjectFromFactoryBean(FactoryBean? factory, String name) { if (factory.isSingleton() containsSingleton(beanName)) { synchronized (this.factoryBeanObjectCache) { Object object this.factoryBeanObjectCache.get(beanName); if (object null) { object doGetObjectFromFactoryBean(factory, name); this.factoryBeanObjectCache.put(beanName, object); } return object; } } return doGetObjectFromFactoryBean(factory, name); }6.3 与BeanPostProcessor的交互FactoryBean与后置处理器的执行顺序InstantiationAwareBeanPostProcessor.postProcessBeforeInstantiationFactoryBean.getObject()BeanPostProcessor.postProcessAfterInitialization这种顺序导致的一个实际影响对FactoryBean产品应用的BeanPostProcessor需要在getObject()内部手动处理。7. 最佳实践与性能考量7.1 线程安全实现建议对于非单例FactoryBean的线程安全处理public class ThreadSafeFactory implements FactoryBeanCounter { private final AtomicInteger idGenerator new AtomicInteger(); public Counter getObject() { return new Counter(idGenerator.incrementAndGet()); } public boolean isSingleton() { return false; } }7.2 资源清理模式实现DisposableBean正确处理资源释放public class ResourceFactory implements FactoryBeanConnection, DisposableBean { private Connection connection; public Connection getObject() throws SQLException { if (connection null) { connection DriverManager.getConnection(url); } return connection; } public void destroy() throws SQLException { if (connection ! null) { connection.close(); } } }7.3 性能优化技巧对于昂贵对象采用双重检查锁实现延迟加载public class ExpensiveObjectFactory implements FactoryBeanExpensive { private volatile Expensive instance; public Expensive getObject() { Expensive local instance; if (local null) { synchronized (this) { local instance; if (local null) { instance local createExpensiveInstance(); } } } return local; } }避免在getObject()中执行耗时操作推荐采用异步初始化public class AsyncFactory implements FactoryBeanData, InitializingBean { private CompletableFutureData future; public void afterPropertiesSet() { future CompletableFuture.supplyAsync(this::loadData); } public Data getObject() throws Exception { return future.get(); // 阻塞直到数据加载完成 } }在SpringBoot项目中FactoryBean的自动装配需要特别注意类型处理。一个常见的陷阱是直接注入工厂产品而丢失了FactoryBean本身的元数据。正确的做法是通过ObjectProvider或特定类型注入Autowired private ObjectProviderMyProduct productProvider; // 安全获取方式 Autowired private MyFactoryBean factoryBean; // 直接注入工厂本身