UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Section: 13.2

  • Key: UML22-267
  • Legacy Issue Number: 10081
  • Status: closed  
  • Source: International Business Machines ( Mr. Adam Neal)
  • Summary:

    The body property of OpaqueBehavior (as well as OpaqueExpression and OpaqueAction) should be declared not unique. The OpaqueBehavior can be used to store user code and the given language that it was written in. The specifiction identifies the lists of languages and bodies to be ordered (and by default unique). It makes sense for the list of languages to be uniuqe, but not the bodies. For example, consider the user has written the same code but in 2 different languages (say c and c+, or written an identical comment in c and c+ and java). Currently the UML specification disallows one to have the same body even though it may semantically make sense in both languages

  • Reported: UML 2.1.1 — Wed, 2 Aug 2006 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    Agreed. In addition, the body and language attributes should be ordered

  • Updated: Fri, 6 Mar 2015 20:58 GMT