Package myorg.relex.one2one

Class Summary

Class	Description
Applicant	This class provides an example of the inverse side of a one-to-one bi-directional relationship.
Application	This class provides an example of the owning side of a one-to-one, bi-directional relationship.
Attendee	This entity class provides an example of a dependent with a relationship to a parent entity that should only exist to support this entity.
Auto	This class is an example of the inverse/parent side of a one-to-one, bi-directional relationship that allows 0..1 and changing related entities.
Auto2	This class is an example of the inverse/parent side of a one-to-one, bi-directional relationship that allows 0..1 and changing related entities.
BoxOffice	This class provides an example of a the owning entity of a one-to-one, uni-directional relationship where the dependent's primary key is derived from the parent, the parent uses a composite primary key, and the dependent used an @EmeddedId and @MapsId.
Coach	This class demonstrates a one-to-one, uni-directional relationship where the foreign key is used to define the primary key with the use of @MapsId
Driver	This class provides an example of the owning/dependent side of a one-to-one relationship where the inverse/parent represents a 0..1 or changing relation.
Driver2	This class provides an example of the owning/dependent side of a one-to-one relationship where the inverse/parent represents a 0..1 or changing relation.
Employee	Provides example of one-to-one unidirectional relationship using a primary key join.
License	This class provides an example of a recipient of cascade actions.
LicenseApplication	This class provides an example initiation of cascade actions to a related entity.
Member	Provides example of one-to-one unidirectional relationship using join table.
Passenger	This entity class provides an example of the owning side of a bi-directional relation where all cascades are being initiated from the inverse side (i.e., not from here).
Person	Target of uni-directional relationship
Player	Provides example of one-to-one unidirectional relationship using foreign key.
Residence	This entity class provides an example of an entity that will get deleted when no longer referenced by its dependent entity in a one-to-one relation.
ShowEvent	This class represents the passive side of a one-to-one uni-directional relationship where the parent uses a composite primary key that must be represented in the dependent entity's relationship.
ShowEventPK	This class will be used as an IdClass for the ShowEvent entity.
ShowTickets	This class provides an example of a the owning entity of a one-to-one, uni-directional relationship where the dependent's primary key is derived from the parent and the parent uses a composite primary key.
Ticket	This entity class provides an example of cascades being originated from the inverse side of a bi-directional relationship.

Enum Summary

Enum	Description
Auto.Type
Auto2.Type
Coach.Type
Member.Role
Player.Position