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:

You can create a Spring Data JPA repository only for an entity with a field annotated with @Id.

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 ability to define a query with the @Query annotation. You can use JPA Palette (1) or Editor Toolbar (2) to write them quickly and without any typos. Choose one of the following types of queries and configure them with the convenient UI.


All that we will consider in the example below can be generated as @Query and as a derived query method. The only difference is that for the derived query method, you can't specify its name because it will be generated automatically according to Naming Conventions for Query.

Let's look at an example of creating a Find Collection Query.

At the top of the window, you can define wrap type for collection and query return type. Moreover, JPA Buddy allows you to generate new Projection interface or DTO class right from this window (just click on the + button).

You can also specify the method name. Still, 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 conditions.

At the bottom of the window, you can specify:

  • whether the parameters will be named or not;
  • whether to use Pageable parameter or not;
  • and so on.

Finally, you can specify fields by which the query result will be ordered.

For the above configuration, the following query will be generated:

        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>> findOwners(@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:

Existing methods/queries modification

To configure the method or query, place a cursor on it and use JPA Inspector:

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 ability 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:

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 (similar to what IntelliJ IDEA Ultimate Edition provides). Place the cursor on the query and click on the “Query edit...” in the JPA Inspector.


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 above configuration the following projection will be generated:

 * A Projection for the {@link Pet} entity
public interface PetInfo {
	Integer getId();

	String getName();

	LocalDate getBirthDate();

	PetTypeInfo getType();

	OwnerInfo getOwner();

	 * A Projection for the {@link PetType} entity
	interface PetTypeInfo {
		Integer getId();

		String getName();

	 * A Projection for the {@link Owner} entity
	interface OwnerInfo {
		String getFirstName();

		String getLastName();

Keep Projections in sync with its JPA entity

As time passes, entities may change, and you need to change projections accordingly. JPA Buddy allows you to synchronize an entity with its projection and vice versa. Read more about this feature in the DTO Generator section.

Projection Declaration Settings

Each project may follow its own conventions for code writing. In the Tools -> JPA Buddy -> Projection Declaration you can configure:

  1. Class name postfix.
  2. Name pattern regexp (the feature is disabled when the field is empty). This option is useful if you use an obligatory naming convention for Projections. It allows JPA Buddy to associate Projection with its JPA Entity using a Projection name only. To specify a placeholder for the simple class name of the target JPA entity, use the (?<entity>.) pattern. E.g., (?<entity>.*(?:Info|Prj|Projection|VO|Vo|View|Request|Browse) means that the MyEntityInfo, MyEntityPrj etc. classes will be considered as a Projections for MyEntity.
  3. Class comment. Defines the comment that will be generated over the Projection interface.
  4. Comment link regexp (the feature is disabled when the field is empty). This option allows JPA Buddy to associate Projection with its JPA Entity. To specify a placeholder for the target entity FQN (Fully Qualified Name) in a comment use the (?<entity>.*) pattern. So, if the regexp is defined as A Projection for the \{@link (?<entity>.*)\} entity it will be resolved in the following Javadoc comment:
 * A Projection for the {@link Pet} entity

Convenient Navigation between Entity and its Projections

As soon as JPA Buddy is able to associate Projection interface with the entity:

  • The Projection interface will appear in the Dto & Projections section in the JPA Structure panel and in the Editor Toolbar (1)
  • The gutter icon will appear in the Projection to ease the navigation to its entity (2)

Auditing Support

Having auditing in a large application is a crucial aspect. With JPA Buddy, you can now effortlessly include commonly used audit fields by utilizing annotations such as @CreatedBy, @CreatedDate, @LastModifiedBy and @LastModifiedDate. What's more, JPA Buddy will notify you if you forget to add the @EnableJpaAuditing annotation to your configuration or if the AuditingEntityListener is not added to the current entity. This leaves even less room for the mistake!