Hey there, let's break down why your TransactionManager bean isn't being picked up by Spring's ComponentScan—even though other beans in the same package are being discovered and injected without issues. The key clue here is that its constructor never gets called, which means Spring isn't even trying to create this bean in the first place.

Here are the most likely culprits and fixes:

• Missing Spring Bean Annotation
  ComponentScan only picks up classes marked with Spring's stereotype annotations like @Component, @Service, @Repository, or @Controller. Double-check your TransactionManager class—if it doesn't have one of these annotations, Spring won't recognize it as a bean.
  Example fix:

  @Component // Or @Service if it's a service-layer class
  public class TransactionManager {
      // Your constructor here
      public TransactionManager() {
          // ...
      }
  }
  

• Private Constructor
  Spring needs access to a public (or at least package-private) constructor to instantiate your bean. If TransactionManager has a private constructor, Spring can't create an instance of it. Make sure the constructor is public:

  // Bad: Private constructor blocks Spring from instantiating
  private TransactionManager() { }
  
  // Good: Public constructor allows Spring to create the bean
  public TransactionManager() { }
  

• Accidental Exclusion from ComponentScan
  Check your Spring Boot application's main class (the one with @SpringBootApplication) to see if you've accidentally excluded the TransactionManager class or its package. Sometimes @ComponentScan might have excludeFilters that are blocking it, or @SpringBootApplication might have an exclude attribute targeting this bean.
  Example of what to avoid:

  // This would exclude TransactionManager from being detected
  @SpringBootApplication(exclude = TransactionManager.class)
  public class YourApp { /* ... */ }
  

• It's a Third-Party Class (Not in Your Codebase)
  If TransactionManager comes from an external library, ComponentScan won't pick it up automatically—you need to explicitly define it as a bean using @Bean in a configuration class:

  @Configuration
  public class TransactionConfig {
      @Bean
      public TransactionManager transactionManager() {
          return new TransactionManager(); // Or configure it with necessary dependencies
      }
  }
  

• Conditional Annotations Preventing Bean Creation
  If TransactionManager has conditional annotations like @ConditionalOnMissingBean, @ConditionalOnProperty, or @Conditional, the conditions might not be met, so Spring skips creating it. Check the class for any such annotations and verify that their required conditions are satisfied (e.g., a property is set in application.properties).

Quick Troubleshooting Steps #

1. First, confirm TransactionManager has a Spring stereotype annotation.
2. Verify its constructor is public (not private).
3. Check your app's main class for any ComponentScan exclusions targeting this bean.
4. If it's a third-party class, register it with @Bean in a config class.
5. Rule out conditional annotations that might be blocking instantiation.

Since other beans in the same package are working, your ComponentScan base package is correctly configured—so the issue is almost certainly specific to how TransactionManager is defined (or not defined) as a Spring bean.

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