JPA Hibernate - Issue with manytomany mapping with extra column in the mapping table?

I think you have a misunderstanding of Idclass annotation. You should take a look at this example Many To Many sample.

I think you have a misunderstanding of Idclass annotation. You should take a look at this example. Many To Many sample If you use a mapping as in the example, hibernate will automatically create a join table for you.

However, if you want to have extra columns on your join table (like user_type), you have to create join table yourself. @Entity @Table(name = "user_bankaccount") public class UserBankAccounts { @Id @GeneratedValue(strategy = GenerationType. IDENTITY) @Column(name = "id") private Long id; @Column(name = "user_type") private String userType; @ManyToOne @JoinColumn(name="user_id") private User user; @ManyToOne @JoinColumn(name="bank_account_id") private BankAccount bankAccounts; } There is no need for userId and accountId fields.

And if you want userbankaccounts to be saved/deleted/updated when bankaccount or user persisted, use cascade annotation in your bankaccount or user entities.

If you want to save the association class when saving the bank or the user class, then you have to set the casscade attribute to the relatin at bank anx/or user class.

I guess its too late to answer this question but adding for reader, kindly refer to this link replace @JoinColumn with @PrimaryKeyJoinColumn so your code will look as follows @ManyToOne @PrimaryKeyJoinColumn(name = "bank_account_id", referencedColumnName = "referencedColumnName ") private BankAccount bankAccounts.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.