jpa | JPA全称Java Persistence API.JPA通过JDK | Object-Relational Mapping library

The userId must be null. That's why there is no delete.

You need to bind the Path Parameters to the method parameters.

So, in the Controller, change

I'm assuming you have missing dependencies on your code generation class path. Once you update your question, I'll update my answer.

jOOQ won't support your generated composite types in generated code out of the box, you'll still have to add forced type configurations for that, possibly embeddable type configurations:

• https://www.jooq.org/doc/latest/manual/code-generation/codegen-advanced/codegen-config-database/codegen-database-forced-types/
• https://www.jooq.org/doc/latest/manual/code-generation/codegen-embeddable-types/

Note that the JPADatabase offers a quick win by integrating with simple JPA defined schemas very quickly. It has its caveats. For best results, I recommend going DDL first (and generate both jOOQ code and JPA model from that), because it will be much easier to put your schema change management under version control, e.g. via Flyway or Liquibase.

The mapping that happens between the output of employeeRepository#findByUuid that is Optional and the method output type Optional is 1:1, so no Stream (calling stream()) here is involved.

All you need is to map properly the fields of Employee into EmployeeDTO. Handling the case the Optional returned from the employeeRepository#findByUuid is actually empty could be left on the subsequent chains of the optional. There is no need for orElse or findFirst calls.

Assuming the following classes both with all-args constructor and getters:

You are violating the JPA spec by accessing the persistence context in a lifecycle listener.

See the JPA Specification 4.2 Section 3.5.2

In general, the lifecycle method of a portable application should not invoke EntityManager or query operations, access other entity instances, or modify relationships within the same persistence context. A lifecycle callback method may modify the non-relationship state of the entity on which it is invoked.

"a portable application should not" is the specification way of saying: Don't do that, anything might happen. Maybe the world ends.

The fix is not to do that. Maybe be preloading the currently logged in user and reference it so you may access it in your entity listener and do not set a reference to the user, but simple store its id or similar.

As you have many to one mapping in Appointment entity. you could write the below query in AppointmentRep

List findAllByPatientId(int id);

https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#repositories.query-methods.query-creation

Missing parentheses or commas have been known to throw this error.

I have managed to figure out the problem. The issue was related to tomcat configuration in /conf/server.xml. Multiple Hosts will trigger the context loader to be triggered for each. I was keeping the default appBase to webapps for all host thus triggering the ContextLoader of each my war for each host. Another reason the ContextLoader will triggered multiple times as well is defining the option inside unless you need to load something external to your war. I recommend reading specs: https://tomcat.apache.org/tomcat-4.1-doc/config/host.html

Create a DTO that represents a row in your HTML:

You need to add this to the app config: