Spring - @Repository annotation in service class

Question

What is the point of putting @Repository in service class CustomerServiceImpl and is it a good practice in this example, my understanding it is not needed for any interfaces that extend JpaRepository and exception translation already included. As far as I understand @Repository "should" be on repository class?

@Repository
@Transactional(readOnly = true)
public class CustomerServiceImpl implements CustomerService {

  @PersistenceContext
  private EntityManager em;

  @Autowired
  private CustomerRepository repository;
  ...
}



@Transactional(readOnly = true)
public interface CustomerRepository extends JpaRepository<Customer, Long> {}

Just quote from your given link The class is annotated with @Repository to enable exception translation from JPA exceptions to Spring’s DataAccessException hierarchy. and in article refactored the code in next portion to describe details of repository model — Eklavya
– Eklavya, Commented Aug 19, 2020 at 19:54

Gopinath · Accepted Answer · 2020-08-19 20:44:51Z

1

Technically, the @Repository annotation may not be absolutely necessary in the given example for the CustomerServiceImpl class.

However, the use of @Repository annotation optimizes the 'search' and 'List all' operations by implementing the 'Domain Driven Design' pattern.

Example: The underlying repository can be a Relational database / No-sql database / a CSV file. Use of @Repository will hide the implementation complexity from 'Search' and 'List all' operations in this case.

answered Aug 19, 2020 at 20:44

Gopinath

4,9971 gold badge17 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Spring - @Repository annotation in service class

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related