标注@Primary的JpaRepository未被@Autowired注入问题排查

Hey there! Let's walk through what's probably going on with your Spring setup, since you mentioned you're hitting an issue but aren't sure why. First, let's clarify your code structure to make it easier to diagnose:

Your Code Breakdown #

UserService Interface

public interface UserService {
    List<User> findAll();
}

SimpleUserService Implementation

@Component
public class SimpleUserService implements UserService {
    private List<User> users = Arrays.asList(new User());

    @Override
    public List<User> findAll() {
        return Collections.unmodifiableList(users);
    }
}

UserRepository (Spring Data JPA)

@Repository
@Primary
public interface UserRepository extends JpaRepository<User, Long>, UserService {
    // Spring Data JPA auto-generates the implementation here
}

Most Likely Issues & Fixes #

Since you didn't share the exact error message, let's cover the top problems that pop up with this kind of setup:

1. Spring isn't scanning your JPA Repository
   Spring Data JPA needs to know where to look for your repository interfaces to generate their dynamic proxy beans. If your UserRepository is in a package that's not covered by @EnableJpaRepositories or your app's default scan, it won't get created.

• Fix: Add @EnableJpaRepositories to your main application class, pointing to your repo package:

  @SpringBootApplication
  @EnableJpaRepositories(basePackages = "com.yourteam.yourapp.repositories")
  public class YourApplication {
      public static void main(String[] args) {
          SpringApplication.run(YourApplication.class, args);
      }
  }
  

  Or just make sure your repository lives in a subpackage of your main app class—Spring Boot auto-scans those by default.

2. Ambiguous bean resolution (even with @Primary)
   You added @Primary to UserRepository to make it the default UserService bean, but sometimes Spring's dynamic proxies can throw off bean resolution.

• First, double-check that UserRepository actually implements UserService (you said it's a UserService implementation, so confirming the interface extends both JpaRepository and UserService is key).
• If you're still getting a NoUniqueBeanDefinitionException, use @Qualifier explicitly when injecting to pick the bean you want:
  For the JPA repo:

  @Autowired
  @Qualifier("userRepository") // Matches the default bean name (lowercase interface name)
  private UserService userService;
  

  For the simple service:

  @Autowired
  @Qualifier("simpleUserService") // Lowercase class name
  private UserService userService;
  

3. SimpleUserService isn't being detected
   If SimpleUserService is in a package outside your app's default scan range, Spring won't register it as a bean.

• Fix: Either move the class to a subpackage of your main app, or add @ComponentScan to your main class pointing to your services package:

  @SpringBootApplication
  @ComponentScan(basePackages = "com.yourteam.yourapp.services")
  public class YourApplication { ... }
  

4. Dynamic proxy type mismatch
   By default, Spring Data JPA uses JDK dynamic proxies, which only work with interfaces. If you're trying to inject UserRepository as a concrete class (instead of UserService), you'll get a type cast error.

• Fix: Stick to injecting the UserService interface, or enable CGLIB proxies by adding this to your application.properties:

  spring.data.jpa.repositories.proxy-target-class=true
  

Quick Debug Tip #

Turn on debug logging for Spring's bean factory to see exactly which beans are being registered:

logging.level.org.springframework.beans.factory=DEBUG

This will show you if either of your UserService implementations is missing, or if there's a conflict you didn't catch.

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