Spring Data JPA VS Lombok

Please note: The H2 database was chosen for simplicity. You can replace it with any other database technology and use the Spring Boot JPA to connect. The demo application will still work.

What you are trying to do is not supported in JPA/JPQL or Spring Data (see here) Not even all databases support that syntax as far as I'm aware. You either need to concat the columns or add functionality to do this yourself, perhaps a Hibernate UserType will work.

There was also a discussion in the Spring Data JPA project repo surrounding the documentation as well: https://github.com/spring-projects/spring-data-jpa/issues/2055

There is a small typo on the second issue, I have tried opening a PR myself to fix it https://github.com/spring-projects/spring-data-jpa/pull/2869. I hope i haven't messed up something lol.

data-jpa: Spring Data JPA, makes it easy to create JPA-based repositories

This repository is an example application for the Spring Boot framework that employs the Netflix DGS framework to expose a GraphQL API and that interacts with a PostgreSQL DBMS via Spring Data JPA.

I'm using Spring Data JPA as a persistence framework. Therefore, those classes are Hibernate entities.

By two different former developers, one from QueryDSL and the other RSQL JPA Spec (Criteria API), both mention that it is a Java issue mentioned here (since 2015...): https://github.com/spring-projects/spring-data-jpa/issues/1115

If you go with hibernate note that there are a few different ways to use it. It can be used standalone and it can be used as a JPA implementation. If you use Spring and use hibernate as a JPA implementation then a popular Spring data layer abstraction is Spring Data which has JPA support with its Spring Data JPA library (https://spring.io/projects/spring-data-jpa)

The above class maps the json data to a java object we can work with. We use Lombok to generate constructors, getters and setters for our code and the Jackson Project to handle serialization and deserialization of json to pojo . We know the response is an array of objects representing the coffee and so above data structure is fit for this.

Almost a decade ago, I started reducing my boilerplate (and saving time with Lombok. It made my life much easier, simple as that. Ever since I've been looking into finding the smoothest solutions for saving time rather than handling all of it myself.

Lombok is a widely used library that simplifies Java code. The @NonNull annotation helps enforce non-null parameters, generating appropriate null checks:

Project Lombok

I gotta agree with /u/rzwitserloot I don't see anything in the lombok repo that indicates they have their "own compiler". I see the "reaching into javac internals" but that's it.

i looked into that and found this: https://github.com/projectlombok/lombok/issues/2310

Funny enough; /u/rzwitserloot is the author of Lombok, one of the most widely used Java libraries in the world. So it's not really some kind of random-ass Redditor they're having a discussion with either.

This removes the need to add the 'Project Lombok' library (and going through a phase of installing it in your Eclipse IDE; old school devs know what I am talking about) and speeds up development time. Java 14 added a new feature of 'Records' which allows you to do the same, but it doesn't offer a 'copy' method to ease your object creation and also enforces the 'final' keyword for variables making them immutable.

I get the main criticisms of Java, i.e. its verbosity and the requirement for a lot of boilerplate code, and understand why some people switched to Kotlin. But by using libraries such as lombok you can get rid of most of it and suddenly the incentives for switching aren't that big anymore. And in the end it's all JVM bytecode anyways.

I usually use this... https://projectlombok.org/