Given that you've defined the Enterprise
->Employers
association with @OneToMany
, which means that an Employer
belongs to only one Enterprise
, you should be using @ManyToOne
, meaning that every Employer
belongs to max. 1 Enterprise
, but an Enterprise
can reference many Employers
.
You can define the association specifics (join columns, etc) in one of the sides only, using the mapped-by
attribute in the annotation:
@Entity
class Enterprise
{
@OneToMany(mapped-by="enterprise")
public List<Employee> getEmployers()
// implementation
@OneToOne
public Employee getPresident()
// implementation
}
@Entity
class Employee
{
@ManyToOne
@JoinTable ( name="Enterprise", joinColumns={ @JoinColumn(name="ENT_ID", referencedColumnName="ENT_ID") }
public Enterprise getEnterprise()
// implementation
}
In case an Employer
could be president of a different Enterprise
in which he is employed (seems unlikely, unless one can be president of an enterprise without being employed by it), and in case you needed to access the Enterprise
of which the Employer
is president from the Employer
entity, you would need to add another association, ideally with @OneToOne
(you would encounter problems, because @OneToOne relations require both entities to have the same @Id class). In this case I would annotate the getPresidedEnterprise()
method on Employer
with @ManyToOne
for practical reasons.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…