Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Papyrus for Real Time » Do activities
Do activities [message #1753119] Thu, 02 February 2017 03:18 Go to next message
Juergen Dingel is currently offline Juergen DingelFriend
Messages: 42
Registered: January 2015
Member
The tool allows the specification of a 'do activity' for a state. But, the code generator appears to ignore it and, I heard, UML-RT does not allow do activities. Should do activities be removed from Papyrus-RT?

Thanks

Juergen
Re: Do activities [message #1753175 is a reply to message #1753119] Thu, 02 February 2017 12:57 Go to previous message
Peter Cigehn is currently offline Peter CigehnFriend
Messages: 49
Registered: September 2014
Member
That's right, UML-RT does not support the notion of do activities.

So yes, it probably should be "removed" from Papyrus-RT. Keep in mind that currently the UML tab in the properties view, "inherited" from Papyrus, is still visible and possible to use in Papyrus-RT. On this tab everything that is in UML is exposed, even though it might not be part of UML-RT.

To be really sure, one should for now only use the the UML-RT tab in the properties view in the context of Papyrus-RT, to ensure that only properties relevant to UML-RT are visible and possible to change. The UML-RT tab in the properties view is the customized tab, with UML-RT specific behavior, specifically made for Papyrus-RT and UML-RT.

Some types of model elements, e.g. a state in a state-machine, don't (yet) have a UML-RT specific tab, so some care is needed for those elements, e.g when editing entry and exit code. Eventually there will be tooling in place for editing entry and exit code for states using a separate code snippet view, where it will hopefully be more clear that you cannot enter any "do activity" code. See bug 494288 for more information.

It is still not decided if and how the UML tab shall be removed in the context of Papyrus-RT, since there are uses cases and scenarios were UML-RT are being used together with "full" UML, and completely hiding the UML tab could limit the use of UML-RT in combination with UML. But this can probably be solved by having different "configurations" of Papyrus-RT for different usages, e.g. a Papyrus-RT configuration which have removed the UML tab in the properties view and only exposes the UML-RT tab with the subset of properties relevant for UML-RT.

So, for now, try to only use the UML-RT tab in the properties view, and for those model elements that (still) only have a UML tab, be careful about which properties actually are applicable to UML-RT.

/Peter Cigéhn
Previous Topic:why no triggerless transitions out of non-pseudo states?
Next Topic:What is the difference between a Choice and a Junction?
Goto Forum:
  


Current Time: Tue Nov 13 18:12:05 GMT 2018

Powered by FUDForum. Page generated in 0.02212 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top