Eclipse Community Forums: Papyrus

Home » Modeling » Papyrus » SignalEvent( )

Tue, 26 February 2013 11:11

Eclipse User

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?

Re: SignalEvent [message #1014938 is a reply to message #1014872]

Tue, 26 February 2013 16:20

Eclipse User

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 #1015027 is a reply to message #1014938]

Wed, 27 February 2013 03:50

Eclipse User

I mean I want a SignalEvent to represent a specific instance of an active class having received a signal.

Re: SignalEvent [message #1015069 is a reply to message #1015027]

Wed, 27 February 2013 06:06

Eclipse User

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.

Re: SignalEvent [message #1015072 is a reply to message #1015027]

Wed, 27 February 2013 06:05

Eclipse User

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

Re: SignalEvent [message #1261966 is a reply to message #1015069]

Mon, 03 March 2014 00:55

Eclipse User

A SignalEvent instance is supposed to have an association to exactly one Signal instance (See abstract syntax in Event section of the UML spec). I cannot figure out how to make this association. Nothing in the properties tab for it.

This is an important feature to support Executable UML. I need to relate a Trigger to a SignalEvent and from there to a Signal with attributes. The UML provides what I need but I cannot figure out how to define the reference from SignalEvent to Signal with Papyrus.

Did I miss it?

Thank you,
Dan

Re: SignalEvent [message #1262110 is a reply to message #1261966]

Mon, 03 March 2014 04:20

Eclipse User

Hi Dan,

Papyrus provides a standard set properties views, which are a subset of what's available in UML. In most cases, this should be sufficient, but we may have forgotten a few important properties for some elements.

If you think that something is missing, please add a comment on this bug:

Bug 358077: [Property View - UML] The UML property view should be improved for usability concerns
https://bugs.eclipse.org/bugs/show_bug.cgi?id=358077

In this case, it seems that the SignalEvent#signal property is missing.

Regards,
Camille

Re: SignalEvent [message #1270424 is a reply to message #1262110]

Wed, 12 March 2014 21:00

Eclipse User

I now see that I can use the Advanced view of the Properties tab to set the signal for signalEvents.

/Dan

Previous Topic:	eclipse.ini memory settings for large papyrus projects
Next Topic:	Signal Attributes not in Diagrams

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 00:18:04 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter