Description Artem Tikhomirov 2007-06-15 15:06:34 EDT

Sample model:
class "Model" {
  containment ref "requirements" {
    upperBound : -1;
    type : "Requirement"
  }
}
class "Requirement" {
  containment ref "children" {
    upperBound : -1;
    type : "Requirement"
  }
}

Model maps to dialgram, two top node mappings use Requirement - one with containment feature aka root requirement, another without containment feature aka child requirement.
Genereted code in VisualIDRegistry#getNodeVisualID checks only for metaclasses, hence, can't tell the two and for any Requirement instance passed always returns first visualID, though the instance may be either from within Model (and then it's root) or from within Resource (and then it's child req).

Right now it's possible to workaround this issue with constraint that explicitly checks for eContainer or smth similar. However, generated code should handle such cases correctly out of the box