Only one setter fires?

Question

Java

Just don't hit.
Through the constructor, when creating an object, I call the setter on password and username, the password is created, but username is not ...
Code of the class entity:

@Entity
@Table(name = "users")
@NoArgsConstructor
@Getter
@Setter
public class User {
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private int id;
    private String name;
    private String email;
    private String password;
    private String userName;

    public User(String name, String email, String password) {
        this.name = name;
        this.email = email;
        setUserName(email);
        setPassword(password);
    }

    private void setUserName(String email) {
        this.userName = email.split("@")[0];
        LoggerFilter.logger.info("User.java: set user name;");
    }

    private void setPassword(String password) {
        this.password = BCrypt.hashpw(password, BCrypt.gensalt());
        LoggerFilter.logger.info("User.java: set password;");
    }
}

Logger:

If a separate method calls the setter on username, then it works.

@PostMapping("sign-up")
    public void signUp(@RequestBody User user) {
        
        user.setUserName(user.getEmail());
        
        userRepository.save(user);

    }

Can you please tell me what is the problem, why can't I call the second setter?
Thanks for the help!

Answer 1

The spider tells me a little that I shouldn't drag Lombok anywhere. This @NoArgsConstructor annotation
creates a constructor with no arguments. Accordingly, when creating a bean, it is called, and not your overloaded one. I would also venture to suggest that you do not pass the userName parameter, respectively, and the setter is not called for it.
IMHO the correct answer is that the wrong constructor is called.

Answer 2

As C4ET4uK already wrote , the problem is with calling the wrong constructor.
Hibernate creates an object with a default constructor, then sets the properties of the object using set methods. Accordingly, Hibernate does not use your constructor to create an object. If the value of the userName
property is not stored in the database (in the user_name column, respectively), then the Hibernate setUserName method will also never be called. Alternatively, you can add a setUserName call to setEmail .