OneToMany
- Implemented Interfaces:
Annotation
If the collection is defined using generics to specify the element type, the associated target entity type need not be specified; otherwise the target entity class must be specified. If the relationship is bidirectional, the OneToMany.mappedBy element must be used to specify the relationship field or property of the entity that is the owner of the relationship.
A OneToMany association usually maps a foreign key column or columns in the table of the associated entity. This mapping may be specified using the JoinColumn annotation. Alternatively, a unidirectional OneToMany association is sometimes mapped to a join table using the JoinTable annotation.
The OneToMany annotation may be used within an embeddable class contained within an entity class to specify a relationship to a collection of entities. If the relationship is bidirectional, the OneToMany.mappedBy element must be used to specify the relationship field or property of the entity that is the owner of the relationship.
When the collection is a java.util.Map, the OneToMany.cascade element and the OneToMany.orphanRemoval element apply to the map value.
Example 1:
One-to-Many association using generics {@snippet : // In Customer class:
- Since:
- JPA 1.0
Public Annotation Attributes
Defaults to no operations being cascaded.
When the target collection is a java.util.Map, the cascade element applies to the map value.
- Since:
- JPA 1.0
- Since:
- JPA 1.0
- Since:
- JPA 1.0
- Since:
- JPA 2.0
Defaults to the parameterized type of the collection when defined using generics.
- Since:
- JPA 1.0