Sometimes, the keys don't match up perfectly between tables... (this very well could be a normalization issue, but I have to work w/ it).
I have worked around it by using custom attributes.
So - it would be nice to see:
<inverse-foreignkey field-ref="collectionClassField" parent-field-ref="classDescriptorField"/>
So if the parent-field-ref attribute is present, OJB would use a different field as the key instead of the primary key...
What does everyone think?
--Bobby
