Spring原型Bean嵌套原型Bean改造及动态实例化方案咨询

方式一：构造函数注入+Spring自动参数传递 #

通过构造函数注入所有依赖（包括下一级服务和Platform），Spring会在创建原型Bean时自动传递Platform参数到整个服务链：

1. 修改每个服务类的构造函数，注入依赖而非手动new：

@Service
@Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
public class ServiceAlphaImpl implements ServiceAlpha {
    private final Platform platform;
    private final ServiceBeta serviceBeta;

    // 构造函数注入Platform和ServiceBeta
    public ServiceAlphaImpl(Platform platform, ServiceBeta serviceBeta) {
        this.platform = platform;
        this.serviceBeta = serviceBeta;
    }

    // 业务逻辑
}

@Service
@Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
public class ServiceBetaImpl implements ServiceBeta {
    private final Platform platform;
    private final ServiceGamma serviceGamma;

    public ServiceBetaImpl(Platform platform, ServiceGamma serviceGamma) {
        this.platform = platform;
        this.serviceGamma = serviceGamma;
    }

    // 业务逻辑
}

@Service
@Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
public class ServiceGammaImpl implements ServiceGamma {
    private final Platform platform;

    public ServiceGammaImpl(Platform platform) {
        this.platform = platform;
    }

    // 业务逻辑
}

2. 获取Bean时直接传递Platform参数：

// 传入自定义Platform实例，Spring会自动将其传递给整个服务链的构造函数
ServiceAlpha alpha = applicationContext.getBean(ServiceAlpha.class, new Platform("OMEGA"));

原理：Spring在创建原型Bean时，会解析构造函数的依赖。当你调用getBean传递Platform参数时，Spring会将该参数注入到ServiceAlphaImpl，同时在解析ServiceAlphaImpl依赖的ServiceBeta时，会复用同一个Platform参数创建ServiceBetaImpl，以此类推完成整个链的初始化。

方式二：ObjectProvider手动传递参数（更可控） #

如果需要更明确地控制参数传递，可以使用ObjectProvider获取下一级原型Bean，并手动传入Platform：

1. 修改服务类构造函数，注入ObjectProvider而非直接注入下一级服务：

@Service
@Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
public class ServiceAlphaImpl implements ServiceAlpha {
    private final Platform platform;
    private final ServiceBeta serviceBeta;

    public ServiceAlphaImpl(Platform platform, ObjectProvider<ServiceBeta> serviceBetaProvider) {
        this.platform = platform;
        // 手动传入同一个Platform创建ServiceBeta实例
        this.serviceBeta = serviceBetaProvider.getObject(platform);
    }

    // 业务逻辑
}

@Service
@Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
public class ServiceBetaImpl implements ServiceBeta {
    private final Platform platform;
    private final ServiceGamma serviceGamma;

    public ServiceBetaImpl(Platform platform, ObjectProvider<ServiceGamma> serviceGammaProvider) {
        this.platform = platform;
        this.serviceGamma = serviceGammaProvider.getObject(platform);
    }

    // 业务逻辑
}

@Service
@Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
public class ServiceGammaImpl implements ServiceGamma {
    private final Platform platform;

    public ServiceGammaImpl(Platform platform) {
        this.platform = platform;
    }

    // 业务逻辑
}

2. 获取Bean的方式和方式一相同：

ServiceAlpha alpha = applicationContext.getBean(ServiceAlpha.class, new Platform("OMEGA"));

优势：明确控制每个依赖的参数传递，避免Spring自动解析可能出现的歧义（比如存在多个Platform类型的Bean时）。

1. 封装Platform上下文：如果多个服务都依赖Platform，可以创建PlatformContext类封装Platform，让服务依赖PlatformContext而非直接依赖Platform，减少重复注入，也方便后续扩展上下文内容。
2. 自定义作用域：如果这种按Platform实例隔离的场景较多，可以自定义一个PlatformScoped作用域，让Spring自动为同一个Platform复用Bean实例，替代原型作用域的频繁创建。
3. 使用配置类管理Bean：通过@Configuration配置类定义Bean，替代@Service注解，更灵活地控制Bean的创建逻辑：

@Configuration
public class ServiceConfig {
    @Bean
    @Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
    public ServiceAlpha serviceAlpha(Platform platform, ServiceBeta serviceBeta) {
        return new ServiceAlphaImpl(platform, serviceBeta);
    }

    @Bean
    @Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
    public ServiceBeta serviceBeta(Platform platform, ServiceGamma serviceGamma) {
        return new ServiceBetaImpl(platform, serviceGamma);
    }

    @Bean
    @Scope(ConfigurableBeanFactory.SCOPE_PROTOTYPE)
    public ServiceGamma serviceGamma(Platform platform) {
        return new ServiceGammaImpl(platform);
    }
}

4. 保持接口与实现分离：继续保留ServiceAlpha、ServiceBeta等接口，实现类依赖接口而非具体实现，提升代码的可测试性和扩展性。
5. 避免硬编码依赖：始终通过构造函数注入依赖，禁止手动new依赖对象，确保Spring容器完全管理Bean的生命周期和依赖关系。

内容的提问来源于stack exchange，提问作者Pavlo Kuchereshko