2.5.2.10.1. Bidirectional Relations
When two fields are logical inverses of each other, they form a
bidirectional relation.
Our model contains two bidirectional relations: Magazine.publisher and Company.mags form one bidirectional relation, and Article.authors and Author.articles form the other.
In both cases, there is a clear link between the two fields that form the relationship.
A magazine refers to its publisher while the publisher refers to all its published magazines.
An article refers to its authors while each author refers to her written articles.
When the two fields of a bidirectional relation share the same datastore mapping, JPA formalizes the connection with the mappedBy property.
Marking Company.mags as mappedBy Magazine.publisher means two things:
-
Company.magsuses the datastore mapping forMagazine.publisher, but inverses it. In fact, it is illegal to specify any additional mapping information when you use themappedByproperty. All mapping information is read from the referenced field. We explore mapping in depth in Mapping Metadata. -
Magazine.publisheris the "owner" of the relation. The field that specifies the mapping data is always the owner. This means that changes to theMagazine.publisherfield are reflected in the datastore, while changes to theCompany.magsfield alone are not. Changes toCompany.magsmay still affect the JPA implementation’s cache, however. Thus, it is very important that you keep your object model consistent by properly maintaining both sides of your bidirectional relations at all times.
You should always take advantage of the mappedBy property rather than mapping each field of a bidirectional relation independently.
Failing to do so may result in the JPA implementation trying to update the database with conflicting data.
Be careful to only mark one side of the relation as mappedBy, however.
One side has to actually do the mapping!
|
|
You can configure OpenJPA to automatically synchronize both sides of a bidirectional relation, or to perform various actions when it detects inconsistent relations. See Managed Inverses in the Reference Guide for details. |