Spring Data JPA


Spring Data JPA is part of the larger Spring Data family that makes it easy to implement JPA-based repositories quickly. JPA Buddy provides a clear UI for generating repositories, projections, queries, etc., for both Java and Kotlin entities. To enable those features, your project should contain dependencies mentioned in the Installation Guide.

Repository Creation

JPA Buddy provides various ways to create repositories to make working with JPA-related objects more convenient for most users. All possible ways to generate repositories in the project are shown in the following video:

In the New JPA Repository window, you can set:

When we have a lot of entities, creating Spring Data repositories one by one becomes a tedious job. With JPA Buddy, you can speed up this process. To create repositories for JPA entities, you need to take three steps. Select entities in the project tree, invoke the JPA Buddy wizard, then adjust your selection. That's it! Look how this feature can speed up the development process:

JPA Structure Repositories

For the most efficient navigation in the project, JPA Buddy groups all repositories for each entity. It doesn't matter if the repositories for the entity are located in different or in the same project package. All repositories related to the entity will be displayed in the "Repositories" section. From here, you can quickly move to the repository implementation or create a new one.

Queries/Methods Generation

Spring Data provides the possibility to define a query with the @Query annotation. To write them accurately and in less time, use JPA Palette. Choose one of the following types of queries and configure them with the convenient UI.


All that will be considered in the example below can be generated not only as a query but also as a method. The difference is that you can configure the method prefix in the Advance panel, and you can’t specify the name for it, because it will be generated automatically in accordance to Naming Conventions for Query.

Let's take a look at the example with Find Collection query creation.

Let's start from the top of the window. You can define one of the possible wrap types for collection, return value and you can also define the name for the method, but if you rest it empty, the name will be generated automatically following Naming Conventions for Query.

The middle of the window contains the table for the query condition configuration.

At the bottom of the window you can specify specific for each query parameters, such as: whether the parameters will be named or not, whether to add the @Async annotation and so on. Here you can also add fields by which the result of the query will be ordered.

For the configuration below, the following query is generated:

@Query("select distinct o from Owner o " + 
       "where upper(o.firstName) like upper(concat(:firstName, '%')) " + 
       "and upper(o.lastName) like upper(concat('%', :lastName, '%')) " + 
       "order by o.lastName") 
CompletableFuture<List<Owner>> findOwner(
  @Param("firstName") String firstName,
  @Param("lastName") @NonNull String lastName,
  Pageable pageable); 

Entity Intention

JPA Buddy also provides intention on the entity attributes leading directly to the query/method creation window. Place the cursor on the desired attribute, press Alt+Enter (or Opt+Enter on Mac), and click on the Create Spring Data repository method. In the opened window, choose the required type of query/method.

Unresolved Reference

Some developers prefer to declare a call to the method that doesn't exist yet first and only then implement it. JPA Buddy will help those developers who adhere to this programming style. Just write the desired signature and move to the query or method creation wizard via special actions:


Spring Data provides several keyword expressions for derived query method names. You can use NameContaining, NameIsContaining, or NameContains - the result is the same. On the one hand, it gives us some flexibility in methods naming. On the other hand, in big teams, different naming for the same actions may be confusing for code reviewers and maintainers. If you have naming standards established for the development team, you can configure JPA Buddy to use only approved keywords for method names generation:

JPA Inspector

Since JPA Inspector is a context-dependent panel intended to modify already existing code, let’s consider the scope related to methods and queries. Once you place a cursor on the method or query you can configure the result, signature, query options, and string.

EntityGraph Support

The EntityGraph feature has been introduced in JPA 2.1, it has been one of the most awaited features for quite a long time. Entity graphs give us another layer of control over data that needs to be fetched. JPA Buddy supports them, so you can build graphs using a handy GUI wizard:

Query Refactoring


Spring Data JPA provides the possibility to run repository queries asynchronously. The correct way to make asynchronous query is not only to add @Async annotation, but also to change the return type to one of the following:

  • Future
  • CompletableFuture
  • ListenableFuture

Learn more about asynchronous query results at the corresponding Spring Data JPA documentation page.

To make query async, place the cursor on the query you want to change and choose the result return type from the drop-down list:

Projection Creation

Sometimes you only need a subset of columns from a table. In such cases, Spring Data JPA projections come in handy, letting you return only required fields from queries.

In the "New Spring Projection" window, you can:
  • Define source root and package;
  • Choose entity class;
  • Set a name for a projection class;
  • Select the fields you want to include.

Also, JPA Buddy allows you to generate Projections for the referenced entities. Select the associated entity, choose the Projection type, and pick the required fields.

For the configuration below the following projection will be generated:

public interface PetInfo {
    Integer petId();

    LocalDate getBirthDate();

    String petName();

    OwnerInfo getOwner();

    PetTypeInfo getType();

    interface OwnerInfo {
        String getFirstName();

        String getLastName();

    interface PetTypeInfo {
        Integer getId();

        String getName();

Dynamic Projection

In Spring Data JPA, projections can also be specified during runtime by using generic repository methods. Add a type class parameter to your repository method to use the same query with different projections. This enables you to define the preferred returned type in your business code.

To make query generic, place the cursor on the query you want to change and check the box “Dynamic projection”.

Query Extracting

Derived query methods are a handy way to define queries. But over time, they may evolve into bulky and unreadable structures you would prefer to transform into neat @Query-annotated methods. This can be easily achieved with JPA Buddy. Place the cursor on the query and click on the “Query extract...” in the JPA Inspector.

Query Autocompletion

For the IntelliJ IDEA Community edition, JPA Buddy provides query autocompletion, as it is in the IntelliJ IDEA Ultimate Edition. Place the cursor on the query and click on the “Query edit...” in the JPA Inspector.