- Ya
- 29 Mei 2026, 18:28 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 7045295
Spring Data JPA derives the repository bean name from the interface's simple class name, not from the @Repository("...") qualifier value, so the prior workaround did not actually prevent the collision with the unrelated mortgage repository at **************** Services scanning both packages (KamoLOS, KamoInitializerService) failed at boot with BeanDefinitionOverrideException for bean 'loanRepository'. Renaming the interface gives Spring a distinct simple class name and so a distinct bean name (personalLoanRepository). @Repository qualifier is no longer needed.