This annotation enables a Spring bean postprocessor to advise all beans with all the PersistenceExceptionTranslator instances found in the container, and provide exception translation just as before. Exception translation is still enabled by the use of the annotation on the DAO. The question now becomes: since Spring Data JPA doesn't depend on the old ORM templates ( JpaTemplate, HibernateTemplate), and they have been removed since Spring 5, are we still going to get our JPA exceptions translated to Spring's DataAccessException hierarchy? The last option has the disadvantage that it either involves XML or burdening the domain class with the queries. The advantages of this API will become more pronounced when dealing with a large number of fixed queries, as we could potentially express these more concisely through a smaller number of reusable blocks. This makes the whole operation much more readable and reusable. The third option, Specifications and Querydsl support, is similar to JPA Criteria, but uses a more flexible and convenient API. define custom queries via JPA Named Queries.use the more advanced Specification and Querydsl support in Spring Data.provide the actual JPQL query by using the annotation.simply define a new method in the interface.To define more specific access methods, Spring JPA supports quite a few options:

As discussed, by implementing one of the Repository interfaces, the DAO will already have some basic CRUD methods (and queries) defined and implemented.

Intellij idea ultimate