Author Topic: Message metaclass in profile  (Read 1024 times)

qwerty

  • EA Guru
  • *****
  • Posts: 10586
  • Karma: +232/-192
  • I'm no guru at all
    • View Profile
Message metaclass in profile
« on: April 04, 2012, 08:37:13 pm »
The Message metaclass has two properties messageKind and messageSort. messageKind seems obvious, but what is messageSort? I tried setting messageKind to Signal but the message still appears as Call. messageSort also does not seem to change anything.

Another bug I'm too tired to send officially.

q.

ewald

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Message metaclass in profile
« Reply #1 on: November 21, 2018, 07:48:28 am »
From UML 2.5.1 Specification:

17.12.20 MessageKind [Enumeration]
17.12.22.1 Description
This is an enumerated type that identifies the type of communication action that was used to generate the Message.
17.12.20.3 Literals
  • complete - sendEvent and receiveEvent are present
  • lost - sendEvent present and receiveEvent absent
  • found - sendEvent absent and receiveEvent present
  • unknown - sendEvent and receiveEvent absent (should not appear)

17.12.22 MessageSort [Enumeration]
17.12.22.1 Description
This is an enumerated type that identifies the type of communication action that was used to generate the Message.
17.12.22.3 Literals
  • synchCall The message was generated by a synchronous call to an operation.
  • asynchCall The message was generated by an asynchronous call to an operation; i.e., a CallAction with isSynchronous = false.
  • asynchSignal The message was generated by an asynchronous send action.
  • createMessage The message designating the creation of another lifeline object.
  • deleteMessage The message designating the termination of another lifeline.
  • reply The message is a reply message to an operation call.

qwerty

  • EA Guru
  • *****
  • Posts: 10586
  • Karma: +232/-192
  • I'm no guru at all
    • View Profile
Re: Message metaclass in profile
« Reply #2 on: November 21, 2018, 09:00:16 am »
You know that I wrote this 6 years ago? UML 2.5 wasn't even thought of that time.

q.