Legacy Issue Number: 3290
Source: NIST ( Conrad Bock)
The Constraint meta-type, in the Extension Mechanisms meta-model, has
two associations with the same association end name on the "opposite"
ends ("constrainedElement"). Assuming that UML meta-classifiers should
adhere to the OCL for regular classifiers, then this is ill-formed
according to OCL 3 of Classifier, p 47:
 No opposite AssociationEnds may have the same name within a Classifier.
self.oppositeEnds->forAll ( p, q | p.name = q.name implies p = q )
The same may be true for the Collaboration meta-type (the
"ownedElement" association end is duplicated), but these two are
specializations of an association inherited from ModelElement, so
perhaps that is acceptable.
Reported: UML 1.2 — Sat, 5 Feb 2000 05:00 GMT
Disposition: Resolved — UML 1.3
No Data Available
Updated: Fri, 6 Mar 2015 21:37 GMT
UML14 — UML RTF 1.4 Issue: Duplicate association end names from Constraint.
- Key: UML14-1000
- OMG Task Force: UML 1.4 RTF