OneToOne has been logically operated in the back end with.
Organization.JAVA
@OneToOne
@JoinTable(name = "OrganizationsDirectors",
joinColumns = @JoinColumn(name = "director_fk"),
inverseJoinColumns = {@JoinColumn(name = "organization_fk")}
)
@PropertyDescriptor(readOnly = false, index = 2)
public Director getDirector() {
return director;
}
Director.JAVA
@OneToOne
@JoinTable(name = "OrganizationsDirectors",
joinColumns = @JoinColumn(name = "organization_fk"),
inverseJoinColumns = {@JoinColumn(name = "director_fk")}
)
public Organization getOrganization() {
return organization;
}
But there is no user interface that operates creation of the initial director.
New Feature
Closed
Major
@OneToOne needs user interface semantics
There is a bug though. The OneToOne association in the back end is not sticking. A test was successfully performed that validates the mappings are working on hibernate. OGNL was implemented to sustain the inverse property of the OwningObjectReferenceDescriptor. This stick issue still persists.