[OJB-64] Correct handling of 1:n references, when the FK-field is declared in the super-classes instead of the referenced class

• Type: Bug
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.3, 1.1 CVS
• Component/s: JDO-API, ODMG-API, OTM-API, PB-API
• Assignee: Jakob Braeuchi
• Reporter: Armin Waibel
• Created: 07/Aug/05 09:16
• Updated: 29/Oct/05 05:45

Description

Problem is the correct handling of 1:n references, when the FK-field is declared in the super-classes.
Example:
Employee<-Manager<-Shareholder
Class 'Consortium' has a 1:n to Shareholder but the FK to Consortium is declared in Manager,

Consortium reference look like
<collection-descriptor
name="shareholders"
element-class-ref="org.apache.ojb.broker.InheritanceMultipleTableTest$Shareholder"
proxy="false"
auto-retrieve="true"
auto-update="object"
auto-delete="object"
>
<inverse-foreignkey field-ref="consortiumKey"/>
</collection-descriptor>

But the 'consortiumKey' is declared in Manager (e.g. because we want to introduce a second 1:n containing all Manager).

More detail see InheritanceMultipleTableTest#testInheritedReferences()