springdoc-openapi VS Spring Data JPA

The issue is that the springdoc-openapi BOM brings an old version of the Spring Framework 6.0, which is incompatible with Spring Boot 3.2. There are several ways to solve this problem: update springdoc, change the order of BOM imports, but the best, in my opinion, is to avoid using the io.spring.dependency-management plugin.

I would suggest using Springdoc

The SpringDoc library comes with lots of annotations to tune your REST API specification precisely. Anyway, that's out of context of this article.

I found SpringDoc, a library that automates the generation of the spec from the source code. It relies on annotations for textual bits (like tags and descriptions), but it also infers stuff from Spring annotations.

This is an API made with Spring Web, uses springdoc-openapi-ui to expose a swagger-ui on http://localhost:8080/swagger-ui/index.html

Libraries like Springdoc or Springfox can do this. These libraries generate the OpenAPI documentation based on your controllers (+ you can apply the OpenAPI annotations on your controllers). This documentation is then exposed as a REST API, for Springdoc these can be found at /v3/api-docs.

Retrieving all endpoints of a service isn't the goal of a service registry like Eureka, so no, you can't get all endpoints of a service. You can use a library like Springfox or Springdoc to enable Swagger/OpenAPI for your project. These libraries generate a JSON REST API (and a user interface) to view all your endpoints. You can even provide additional information (eg. default values, descriptions, ...) by adding some additional annotations on your controllers.

The springdoc-openapi helps automating the generation of API documentation using Spring Boot projects GitHub - springdoc/springdoc-openapi

Our microservice accept http requests: For swagger used Swagger OpenAPI 3. The bank account REST controller, which accept requests, validate it using Hibernate Validator, then call command or query service. The main reason for CQRS gaining popularity is the ability to handle reads and writes separately due to severe differences in optimization techniques for those much more distinct operations.

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)