[ http://issues.apache.org/jira/browse/OJB-64?page=all ]
Jakob Braeuchi updated OJB-64:
------------------------------
Comment: was deleted
> Correct handling of 1:n references, when the FK-field is declared in the
> super-classes instead of the referenced class
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: OJB-64
> URL: http://issues.apache.org/jira/browse/OJB-64
> Project: OJB
> Type: Bug
> Components: JDO-API, ODMG-API, OTM-API, PB-API
> Versions: 1.0.3, 1.1 CVS
> Reporter: Armin Waibel
> Assignee: Jakob Braeuchi
>
> 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()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
