@Entity annotation defines that a class can be mapped to a table. And that is it, it is just a marker, like for example Serializable interface. And why @Entity annotation is mandatory? … well, it is the way how JPA is designed. When you create a new entity you have to do at least two … Read more
You should include cascade=”all” (if using xml) or cascade=CascadeType.ALL (if using annotations) on your collection mapping. This happens because you have a collection in your entity, and that collection has one or more items which are not present in the database. By specifying the above options you tell hibernate to save them to the database when saving their parent.
This is a typical bidirectional consistency problem. It is well discussed in this link as well as this link. As per the articles in the previous 2 links you need to fix your setters in both sides of the bidirectional relationship. An example setter for the One side is in this link. An example setter … Read more
You should include cascade=”all” (if using xml) or cascade=CascadeType.ALL (if using annotations) on your collection mapping. This happens because you have a collection in your entity, and that collection has one or more items which are not present in the database. By specifying the above options you tell hibernate to save them to the database when saving their parent.