@ManyToMany(mappedBy = "foo")
@ManyToMany(mappedBy = "foos") private Set<Bar> bars
and Bar has :
@ManyToMany private Set<Foo> foos
What difference does the location of mappedBy attribute make to a bi-directional relationship , other than whether table is called foo_bar, or bar_foo; and without the mappedBy attribute I get two join tables, both foo_bar and bar_foo.
The documentation says:
If the association is bidirectional, one side has to be the owner and one side has to be the inverse end (ie. it will be ignored when updating the relationship values in the association table):
So, the side which has the mappedBy attribute is the inverse side. The side which doesn't have the mappedBy attribute is the owner.
The owner side is the side which Hibernate looks at to know which association exists. So, for example, if you add a Foo in the set of foos of a Bar, a new row will be inserted by Hibernate in the join table. If, on the contrary, you add a Bar to the set of bars of a Foo, nothing will be modified in the database.
mappedBy tells Hibernate which side of the relationship "owns" the link. In OneToMany or OneToOne, using mappyedBy tells Hibernate that there will be a foreign key in the other table which will be used to store the link.
When it comes to ManyToMany, there is a join table, so neither directly has the link to the other object. However, hibernate still needs to know which is the "owning" side to that is knows how to cascade operations.