Java entity - why do I need an empty constructor?

java entity jpa

2022-08-31 21:28:24

This might sound stupid to you, but why do I need to define an empty constructor in my s?@Entity

Every tutorial I saw said : every entity needs an empty constructor.

But Java always give you a default invisible empty constructor (if you don't redefine one).

Let me clarify.. What I understood by "need" was write.

Meaning: always write an empty constructor in your entity.

example:

@Entity
public class MyEntity implements Serializable {

   @Id
   private String str;

   public MyEntity(){}

   //here getter and setter
}

But Java always gives you this empty constructor when you don't redefine it (write an other one with parameters).

In this case writing this empty constructor seems useless.

答案 1

An empty constructor is needed to create a new instance via reflection by your persistence framework. If you don't provide any additional constructors with arguments for the class, you don't need to provide an empty constructor because you get one per default.

You can also use the @PersistenceConstructor annotation which looks like following

@PersistenceConstructor
public Movie(Long id) {
    this.id = id;
}

to initialise your entity if Spring Data is present in your project. Thus you can avoid the empty constructor as well.

答案 2

But java always give you a default invisible empty constructor (if you don't redefine one).

This statement is true only when you don't provide any constructor in your class. If an argument constructor is provided in your class, then jvm will not add the no-argument constructor.