Spring Data JPA using Hibernate and Java Configuration with Annotations

Last Update: 30 Sep 2018

Spring Data JPA makes it very easy to implement JPA-based repositories. In this tutorial, I’ll show you how to use it to integrate a relational database (PostgreSQL in my example) with a Spring Boot application.

Spring Data JPA using Hibernate and Java Configuration - Thomas Vitale

1. The Project Structure

Before starting, I want to show you the final project structure for your reference. At the end of this tutorial, you should end up with something like this.

The folder structure of the project as seen in IntelliJ IDEA

Throughout the tutorial I’m going to use the following:

  • Spring Boot 2.0.x
  • Gradle 4.10.x
  • PostgreSQL 10.5.

2. Dependencies

First, I’ll create a new Spring Boot project with JPA and PostgreSQL as dependencies. You can easily bootstrap your application with the Spring Initializr.

buildscript {
ext {
springBootVersion = '2.0.5.RELEASE'
repositories {
dependencies {
apply plugin: 'java'
apply plugin: 'eclipse'
apply plugin: 'org.springframework.boot'
apply plugin: 'io.spring.dependency-management'
group = 'com.thomasvitale.jpa'
version = '0.0.1-SNAPSHOT'
sourceCompatibility = 1.8
repositories {
dependencies {
view raw gradle.build hosted with ❤ by GitHub

If you want to use a different database, replace the PostgreSQL with the one you need, for example, MySQL.


I’m using Gradle to manage these dependencies, but you’re free to use Maven instead.

3. JPA Configuration

The easiest way to configure a data source in Spring Boot is by defining some values in the application.properties file and rely on its default behaviour. There are a few implementations of JPA: in this example, I’m using Hibernate.

# DATASOURCE (DataSourceAutoConfiguration & DataSourceProperties)
# JDBC URL of the database.
# Login username of the database.
# Login password of the database.
# JPA (JpaBaseConfiguration, HibernateJpaAutoConfiguration)
# DDL mode. This is actually a shortcut for the "hibernate.hbm2ddl.auto" property. Defaults to "create-drop" when using an embedded database and no schema manager was detected. Otherwise, defaults to "none".
# Whether to enable logging of SQL statements.
# Hibernate additional native properties to set on the JPA provider.
# Fix Postgres JPA Error (Method org.postgresql.jdbc.PgConnection.createClob() is not yet implemented).

If you’re not using PostgreSQL, remember to specify the connection URL and the Hibernate dialect for your database on lines 4 and 18 respectively. Refer to the official documentation to find out all the dialects supported by Hibernate.

4. Data Model

My application allows storing information about people into a database. To collect this information, I need a data model Person. The @Entity annotation let Spring know that the Person class is actually representing a table in my database.

@Table(name = "persons")
public class Person {
@GeneratedValue(strategy = GenerationType.AUTO)
private Integer id;
@Column(name = "first_name", nullable = false)
private String firstName;
@Column(name = "last_name", nullable = false)
private String lastName;
@Column(name = "ssn", nullable = false, unique = true)
private String ssn;
public Person() {
public Person(String firstName, String lastName) {
this.firstName = firstName;
this.lastName = lastName;
public Person(String firstName, String lastName, String ssn) {
this(firstName, lastName);
this.ssn = ssn;
public Integer getId() {
return id;
public void setId(Integer id) {
this.id = id;
public String getFirstName() {
return firstName;
public void setFirstName(String firstName) {
this.firstName = firstName;
public String getLastName() {
return lastName;
public void setLastName(String lastName) {
this.lastName = lastName;
public String getSsn() {
return ssn;
public void setSsn(String ssn) {
this.ssn = ssn;
public String toString() {
return firstName + " " + lastName;
view raw Person.java hosted with ❤ by GitHub

Through the @Table(name = "persons") annotation, I can declare the name of the table corresponding to this data model.

The @Id annotation defines the id field as the primary key. The @GeneratedValue(strategy = GenerationType.AUTO) annotation is used to delegate the database to pick an appropriate strategy for the primary key generation.

With the @Column annotation, I can associate a field with specific constraints. In the example, I’m using it to make some fields not nullable and to make the social security number field unique.

5. Data Repository

After defining a data entity, I need a repository to query my database and perform operations on my data. The PersonRepository class extends the JpaRepository interface, which provides a lot of operations out-of-the-box, including the standard CRUD operations.

You can also add custom operations. I’m going to define methods to query people data by first name, last name and social security number. The best part of it?  Spring Data JPA creates them for me, no implementation required. Awesome!

public interface PersonRepository extends JpaRepository<Person, Integer> {
List<Person> findByFirstName(String firstName);
List<Person> findByLastName(String lastName);
Person findBySsn(String ssn);

The @Repository annotation makes the class auto-detectable as a data repository.

6. Application

The entry point of my application is the Application class, annotated as @SpringBootApplication.

public class Application {
public static void main(String[] args) {
SpringApplication.run(Application.class, args);
view raw Application.java hosted with ❤ by GitHub

7. Demo

Let’s try some CRUD and custom operations to test the application.

public class ApplicationIntegrationTests {
private PersonRepository personRepository;
public void setUp() {
// Save 4 Person objects into the database
personRepository.save(new Person("Sheldon", "Cooper", "123456"));
personRepository.save(new Person("Missy", "Cooper", "234567"));
personRepository.save(new Person("Leonard", "Hofstadter", "345678"));
personRepository.save(new Person("Leonard", "Nimoy", "456789"));
public void cleanUp() {
// Delete all test data
public void testCRUD() {
// Create
Person originalPerson = new Person("Howard", "Wolowitz", "654321");
Person createdPerson = personRepository.findBySsn("654321");
assertEquals(originalPerson.getFirstName(), createdPerson.getFirstName());
assertEquals(originalPerson.getLastName(), createdPerson.getLastName());
assertEquals(originalPerson.getSsn(), createdPerson.getSsn());
// Update
createdPerson.setFirstName("Fruit Loops");
Person updatedPerson = personRepository.findBySsn("654321");
assertEquals(createdPerson.getFirstName(), updatedPerson.getFirstName());
// Delete
public void testFindAll() {
// Get all the people
List<Person> people = personRepository.findAll();
assertEquals(4, people.size());
public void testFindByFirstName() {
// Get all the people with a specific first name
List<Person> people = personRepository.findByFirstName("Leonard");
assertEquals(2, people.size());
public void testFindByLastName() {
// Get all the people with a specific last name
List<Person> people = personRepository.findByLastName("Cooper");
assertEquals(2, people.size());

8. Behind The Scenes: More Control

In the previous example, I relied on the default configuration provided by Spring Data. To get more control, I can either use Java configuration or XML configuration or a mix of the two. I prefer a pure Java configuration.

The following configuration produces the same result as the previous example. Quite useless. However, I wanted to show it to you since I think it provides a better understanding of what’s going on behind the scenes.

@EnableJpaRepositories(basePackages = "com.thomasvitale.jpa.demo.repository")
public class JpaConfig {
private Environment env;
public LocalContainerEntityManagerFactoryBean entityManagerFactory() {
HibernateJpaVendorAdapter vendorAdapter = new HibernateJpaVendorAdapter();
LocalContainerEntityManagerFactoryBean em = new LocalContainerEntityManagerFactoryBean();
return em;
public DataSource dataSource() {
DriverManagerDataSource dataSource = new DriverManagerDataSource();
return dataSource;
public PlatformTransactionManager transactionManager(EntityManagerFactory emf) {
JpaTransactionManager transactionManager = new JpaTransactionManager();
return transactionManager;
public PersistenceExceptionTranslationPostProcessor exceptionTranslation() {
return new PersistenceExceptionTranslationPostProcessor();
private Properties additionalProperties() {
Properties properties = new Properties();
properties.setProperty("hibernate.hbm2ddl.auto", env.getProperty("spring.jpa.hibernate.ddl-auto"));
properties.setProperty("hibernate.dialect", env.getProperty("spring.jpa.properties.hibernate.dialect"));
properties.setProperty("hibernate.current_session_context_class", env.getProperty("spring.jpa.properties.hibernate.current_session_context_class"));
properties.setProperty("hibernate.jdbc.lob.non_contextual_creation", env.getProperty("spring.jpa.properties.hibernate.jdbc.lob.non_contextual_creation"));
properties.setProperty("hibernate.show_sql", env.getProperty("spring.jpa.show-sql"));
properties.setProperty("hibernate.format_sql", env.getProperty("spring.jpa.properties.hibernate.format_sql"));
return properties;
view raw JpaConfig.java hosted with ❤ by GitHub

If you’re not using PostgreSQL, remember to specify the adapter and the driver for your database on lines 33 and 48 respectively.

This kind of configuration comes in handy when we need to customise the JPA configuration, for example, if we want to configure multiple DataSources or multiple EntityManagers. I will write about more advanced configurations in a future article.

9. Conclusion

In this article, I have shown how to configure in a basic way Spring Data JPA to integrate a relational database with a Spring Boot application.

You can find the complete source code on GitHub.


2 Replies to “Spring Data JPA using Hibernate and Java Configuration with Annotations”

  1. What if I dont create the Table in database and set hibernate.hbm2ddl.auto=update? Spring should create the table for me on repository.save. But that is not happening for me on save it is throwing java.sql.SQLException: ORA-00942: table or view does not exist

    1. Setting hibernate.hbm2ddl.auto=update should be enough to make Spring automatically generate the table in the database. Sometimes Oracle throws that exception even if the table exists, but the privileges are not granted. I would check the grants to be sure that everything is fine in the database.

Leave a Reply

Your email address will not be published. Required fields are marked *