创建名为‘xx’的Bean失败但工厂方法存在，求助排查Spring Boot 2配置问题

Hey there, let's troubleshoot this Bean creation issue you're hitting—even though the factory method exists, there are several common gotchas in Spring Boot 2 that could be causing this. Let's walk through possible causes and fixes:

1. Factory Method Accessibility Problems #

• Double-check if your factory method is non-public. Spring needs public access to invoke the method and create the Bean—if it's marked private or protected, Spring won't be able to reach it even if the method exists.
• Fix: Change the factory method to public to ensure the Spring container can access it.

2. Mismatched Bean Name #

• You mentioned the Bean is named 'xx'. Verify that the @Bean annotation on your factory method explicitly specifies this name with @Bean("xx"). If you don't set a name, Spring defaults to using the method name as the Bean ID—so if your method name isn't 'xx', Spring won't map it to the expected Bean name.
• Fix: Either add the explicit name to the @Bean annotation, or rename the factory method to match 'xx'.

3. Missing or Uninjectable Dependencies in the Factory Method #

• Factory methods often rely on other Beans as parameters. If any of those dependent Beans fail to create, or aren't detected by Spring, the target Bean ('xx') will fail to create too—even if the factory method itself exists.
• Fix:
  • Inspect the parameters of your factory method, and confirm each corresponding Bean is properly defined and visible to the Spring container.
  • Check your application logs for earlier Bean creation errors—those are likely the root cause of this failure.

4. Component Scan or Configuration Scope Issues #

• Looking at your configuration, your @ComponentScan is limited to the com.mycompany.user package. If the configuration class containing your factory method isn't in this package, and isn't imported via @Import or another mechanism, Spring won't load that configuration class at all.
• Also, your exclusion of WebMvcAutoConfiguration and WebMvcConfigurationSupport might cause conflicts if the factory method is related to web MVC components—worth checking if that's the case.
• Fix:
  • Ensure the configuration class with the factory method is in com.mycompany.user, or add its package to the basePackages list in @ComponentScan.
  • If the configuration class is outside the scan range, use @Import to add it to your main configuration class.

5. Type Conflicts with Existing Beans #

• If multiple Beans return the same type, Spring's autowiring logic might get confused, especially if you're not explicitly referencing the 'xx' Bean name. This can make it seem like the factory method isn't being used, even though it exists.
• Fix: Use @Qualifier("xx") alongside @Autowired when injecting this Bean to explicitly target the correct one, and double-check the @Bean annotation's name matches 'xx'.

6. Redundant Annotation Conflicts (Spring Boot 2 Specific) #

• In Spring Boot 2, @SpringBootApplication already includes @Configuration, @EnableAutoConfiguration, and @ComponentScan. Your current configuration repeats these annotations, which can lead to unexpected behavior (like conflicting scan rules or auto-configuration exclusions).
• Fix: Simplify your configuration class to avoid redundant annotations, like this:

  @SpringBootApplication(
      exclude = {WebMvcAutoConfiguration.class, WebMvcConfigurationSupport.class},
      basePackages = {"com.mycompany.user"},
      excludeFilters = {@Filter(type = FilterType.ASSIGNABLE_TYPE, value = RemoteUserManagement.class)}
  )
  @PropertySource("classpath:application.properties")
  @Import({WebSecurityInitializer.class})
  @EnableTransactionManagement
  @EnableJpaRepositories(basePackages = {"com..."})
  public class YourApplication {
      // Application code here
  }
  

  This reduces the chance of configuration clashes that could interfere with Bean creation.

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