[news.eclipse.modeling.mdt.uml2.ocl] Re: Using OCL to specify derived Re

[JG <jguni@xxxxxx>]

Okay, I should have stayed with the DerivedSubsetEObjectEList as you
suggested... when I use it, everything behaves as expected, e.g., when I
add a column to a table, the column also shows up in the "content" List
of the namespace (Table is a Namespace) and vice versa. So this just
makes me wonder what the SupersetSuperset...ELists are actually there
for. And what is the purpose of DerivedEObjectEList

When I used, e.g., SubsetSupersetEObjectWithInverseEList, if I add a
column via the getColumns() EList, it shows up both in the content and
ain the columns EList. If I add a Column to the columns EList, it
doesn't show up. So is it meant to be used if a referenced object is not
part of a subset by virtue of its type, but by explicit adding?

If I observed correctly, the sourceFeatureIds must always point to the
root reference of the derivation hierarchy, i.e., a sourceFeature must
not itself be implemented by a DerivedSubsetEObjectEList.



Regards

Jürgen