-
Key: UML14-969
-
Legacy Issue Number: 3140
-
Status: closed
-
Source: OpenModeling ( Jos Warmer)
-
Summary:
We can imagine packages
Package1 and Package2, both containing the class X, but we
are free to use scope resolution to refer to these two different
classes as Package1::X and Package2::X.However, we then should also be able to specify constraints on
these classes. To do so, the context definition should allow the
fully scoped class name to be used, like incontext Package1::X inv:
-
Reported: UML 1.2 — Fri, 17 Dec 1999 05:00 GMT
-
Disposition: Resolved — UML 1.3
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 21:37 GMT
UML14 — textual syntax cannot deal with identical class names in different package
- Key: UML14-969
- OMG Task Force: UML 1.4 RTF