You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 23, 2023. It is now read-only.
I have a JPARepository that implements another interface. The idea being that alternative implementations of the same interface could be applied. It's a conversation starter with students.
e.g.
public interface CharityRepositoryJPA extends JpaRepository<Charity, Long> , CharityRepository
I then have a service class that depends on CharityRepository. The Spring extension picks up the JPA repository as a component, but doesn't pick up the dependency.
Is there a way of naming the interfaces so that the dependencies are picked up correctly? At the moment, I seem to have to make the service class depend on the JPA interface directly.
Thanks
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a JPARepository that implements another interface. The idea being that alternative implementations of the same interface could be applied. It's a conversation starter with students.
e.g.
I then have a service class that depends on
CharityRepository
. The Spring extension picks up the JPA repository as a component, but doesn't pick up the dependency.Is there a way of naming the interfaces so that the dependencies are picked up correctly? At the moment, I seem to have to make the service class depend on the JPA interface directly.
Thanks
The text was updated successfully, but these errors were encountered: