see atached my example files Feature and FeatureOption.
Feature has featureId as PK, FeatureOption has featureId + optionId as PK.
In my case there is a 1:n unidirectional relation from Feature to FeatureOption.
This runs successful on JBos 3.2.1 ff.
Thanks, but this is not exactly answer to my question.
Imagine FeatureOption has cmr-field:
public abstract FeatureLocal getFeature();
I was wondering if (and how) can this field be part of a composite pk (to make this relationship identifying).