|Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] [DSML][Profile] Look for your point of view against derived property implementation|
If we missed an option, please do not hesitate to add. I guess we should go for the most efficient first and secondly for the most maintainable.
My two cents.
Envoyé depuis mon smartphone Samsung Galaxy.
-------- Message d'origine --------
De : SMAOUI Asma <Asma.SMAOUI@xxxxxx>
Date : 21/12/2017 16:11 (GMT+01:00)
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] [mdt-papyrus.dev] [DSML][Profile] Look for your point of view against derived property implementation
Papyrus team manage to choose only one pattern to be used to get the value of a derived property in a static profile.
As mentioned in a previous discussion https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg03313.html there seems to be 3 methods:
1. Generate code + modify the getter method and add a @generated Not annotation (The one used in MARTE)
2. Generate code + override factory in extension point (The one used in SysML 1.4)
3. Generate code (with UML2 option) + add @generated Not (but only in specific packages named operation) (used in Moka project and preferred by Christian Damus J )
Please feel free to express your preference about those 3 different patterns.
Back to the top