@Repository annotation in Spring Boot

The Spring @Repository annotation is a specialization of the @Component annotation which indicates that an annotated class is a “Repository”, which can be used as a mechanism for encapsulating storage, retrieval, and search behavior which emulates a collection of objects

1. @Repository annotation

In spring framework, @Component annotation marks a java class as a bean so the component-scanning mechanism can pick it up and pull it into the application context.

As @Repository serves as a specialization of @Component, it also enable annotated classes to be discovered and registered with application context.

This annotation is a general-purpose stereotype annotation which can be applied over DAO classes as well as DDD-style repositories. Individual teams may use as appropriate.

import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;
import com.howtodoinjava.demo.model.EmployeeEntity;
public interface EmployeeRepository
        extends JpaRepository<EmployeeEntity, Long> 

2. DataAccessException translation

The @Repository annotation can have a special role when it comes to converting database exceptions to Spring-based unchecked exceptions.

For example, when we work with Hibernate and we do not use a Spring template (e.g. JdbcTemplate) to interact with database. In this case, if hibernate threw an exception then spring will not convert it to Spring-based exception.

To automatically convert such non-spring exceptions to spring exceptions, we shall annotate Hibernate DAOs with @Repository. This way, PersistenceExceptionTranslationPostProcessor will applly persistence exception translation and converts native resource exceptions to Spring’s DataAccessException hierarchy.

3. Testing a @Repository class with @DataJpaTest

Test a repository class is usually done by using an in-memory database and test cases that bootstrap a Spring ApplicationContext usually through the test context framework.

In Spring boot applications, we can use @DataJpaTest annotation that focuses only on JPA components. This annotation will disable full auto-configuration and instead apply only configuration relevant to JPA tests.

By default, tests annotated with @DataJpaTest are transactional and roll back at the end of each test. They also use an embedded in-memory database.

import org.junit.Assert;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.orm.jpa.DataJpaTest;
import org.springframework.test.context.junit4.SpringRunner;

import com.howtodoinjava.demo.model.EmployeeEntity;
import com.howtodoinjava.demo.repository.EmployeeRepository;

public class EmployeeRepositoryTest 
	EmployeeRepository repository;
	public void testRepository() 
		EmployeeEntity emp = new EmployeeEntity();

Drop me your questions related to Spring Boot @Repository example as discussed above.

Happy Learning !!

Was this post helpful?

Join 7000+ Fellow Programmers

Subscribe to get new post notifications, industry updates, best practices, and much more. Directly into your inbox, for free.

Leave a Comment


A blog about Java and its related technologies, the best practices, algorithms, interview questions, scripting languages, and Python.