-
Key: SOAML-17
-
Legacy Issue Number: 13527
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Cory Casanave)
-
Summary:
The requirements for message type match almost exactly with the requirements for signal, yet <<MessageType>> can not be applied to signal which requires yet another model element be created to wrap it. Having message types as signals is the most natural representation for an async protocol as these do not require "wrapping" the messages in operations.
Suggested Resolution: Allow <<MessageType>> to be applied to <<Signal>> -
Reported: SoaML 1.0b1 — Thu, 19 Feb 2009 05:00 GMT
-
Disposition: Resolved — SoaML 1.0
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT