| SignalEvent [message #1014872] |
Tue, 26 February 2013 11:11  |
 Andrea Sindico
Messages: 250
Registered: November 2010 |
Senior Member |
|
|
As far as I understand a SignalEvent can be used to catch a fired Signal that matches a Reception on a receiver.
However, although it is clear how to relate a SignalEvent to a Signal (via the homonym property)I couldn't reduce the scope to a specific reception associated to that signal.
Is there any way to do this?
Follow me on Twitter @andreasindico
|
|
|
| Re: SignalEvent [message #1014938 is a reply to message #1014872] |
Tue, 26 February 2013 16:20  |
|
Hi Andrea,
what do you mean by "couldn't reduce the scope to a specific reception
associated to that signal". I just understand the question.
Regards,
Marc-Florian
"Andrea Sindico" schrieb im Newsbeitrag
news:kgimr0$jfh$1@xxxxxxxxe.org...
As far as I understand a SignalEvent can be used to catch a fired Signal
that matches a Reception on a receiver.
However, although it is clear how to relate a SignalEvent to a Signal (via
the homonym property)I couldn't reduce the scope to a specific reception
associated to that signal.
Is there any way to do this?
--
Follow me on Twitter https://twitter.com/andreasindico
|
|
|
|
| Re: SignalEvent [message #1015069 is a reply to message #1015027] |
Wed, 27 February 2013 06:06 |
Andrea Sindico
Messages: 250
Registered: November 2010 |
Senior Member |
|
|
I gues I may use the MARTE GCMTrigger stereotype which, according to the MARTE specification:
Quote:extends the UML Trigger metaclass. Within UML, triggers can natively be related to a particular port.
Additionally, the GCMTrigger can be related to a particular feature of a FlowPort or ClientServerPort. It is thus possible
to specify reactions that are, for example, related to the occurrence of a specific event on a given non-atomic port. For
example, if we consider a non-atomic flow port proving an interface defining two flow-property (e.g., a time and a speed),
the designer may specify individual reaction to whatever received information.
Follow me on Twitter @andreasindico
|
|
|
| Re: SignalEvent [message #1015072 is a reply to message #1015027] |
Wed, 27 February 2013 06:05 |
|
A trigger may have a Port, so you could distinguish the instances of the
receiving class by the Port on which the event was received. A port belongs
to an EncapsulatedClassifier which might be an active class.
In general, the Classifier that owns the state machine is supposed to
receive the event - of course, only if the state machine is contained in a
context classifier. In case of contex-free state machine, you could use the
Port to indicate which classifier is supposed to receive the event.
HTH,
Marc-Florian
"Andrea Sindico" schrieb im Newsbeitrag
news:kgkhdg$43k$1@xxxxxxxxe.org...
I mean I want a SignalEvent to represent a specific instance of an active
class having received a signal.
--
Follow me on Twitter https://twitter.com/andreasindico
|
|
|
Powered by
FUDForum. Page generated in 0.02827 seconds
] 
Search
Help
Register
Login
Home
