Description Alex Shatalin 2006-02-14 14:11:20 EST

Currently on ECore sample diagram each ERreference instance is represented as a single link on a diagram. Create EMF model with the following elements:

- Class1, Class2 EClasses
- EReference1 from Class1 to Class2 
- EReference2 from Class2 back to Class1
- specify EReference2 as an "EOpposite" for EReference1.

Initialize diagram using this model -> two links (for EReference1 and EReference2) will be created. Both EReferences should be represented as a one link with two roles - "client" and "supplier" (like association link in UML). 

If EReference1 is "containment" reference then link should be created on diagram from Class1 to Class2 (in EReference1 direction). If both references are not "containment" - link could be created in any direction.

This feature could be implemented by introducing special subclass of LinkModelFacet describing "link merge". Link merge in addition to the normal LinkModelFacet properties will store reference to another GenLink (an opposite link) and some additional constraints. 

Logic could be the following: if link instance which corresponds to the "opposite" GenLink found in the model and all the constraints are evaluated successfully, "opposite" link should be removed from diagram (or hidden?), "direct" link should show "opposite" link properties in addition to it's own.