Uses of Package
myorg.relex.one2one

Packages that use myorg.relex.one2one

Package	Description
myorg.relex.one2one

Classes in myorg.relex.one2one used by myorg.relex.one2one

Class and 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.
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.
Auto.Type
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.
Auto2.Type
Coach.Type
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.
License This class provides an example of a recipient of cascade actions.
Member.Role
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.Position
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.
Ticket This entity class provides an example of cascades being originated from the inverse side of a bi-directional relationship.