Java's doubts

Using a Java Record

When studying for a project that is starting, I came across the situation of using Record or a class using JPA.

Behaviors

I ended up seeing that Record does not behave in the same way as a class using Lombok, due to the fact that it creates attributes as Final. Today I'm trying to mature my sense of using it.

-- It is not allowing me to enter the encrypted password value because it initializes the object and cannot be changed. When I start the object with the password already encrypted I have a problem because it doesn't have the ID

Previous projects

All the projects I participated in, they always had an ORM structure, with JPA|Hibernate.
I always tried to maintain the structure because I understood that it was easy to read and well structured. But I always worked with the normal class and building with the lombook characteristics and configurations for creating the database.

Current studies

Now I'm trying to adjust my knowledge of Record's structure, to understand whether the problem is my understanding or Record, which will always behave this way.

The above is the detailed content of Java's doubts. For more information, please follow other related articles on the PHP Chinese website!