Hi Daniel,
Ok, i figured it out to create the right elements. In the use case mentioned i had to create some nodes that do not reside in the rule on UML level (e.g. the classifier of the instance spec).
That way it works to create these edges on the RHS.
Thanks,
Johannes
Am 14.09.2017 um 19:34 schrieb Daniel
Strüber:
Hi Johannes,
generally, you don't need to specify all elements of an input
model - in fact, doing so would very much contradict the idea of
rules, which are meant to be applicable to many different input
models. At its core, a rule specifies (i) a pattern that is
matched against (possibly much larger) input models, and (ii) some
change actions to modify these models if a match was found.
Your use-case of generating rules from a UML model sounds like a
very specialized use of rules. I think we could help you better if
you could describe the context and purpose of your example rule in
more detail.
Best regards,
Daniel
Am 14.09.2017 um 18:25 schrieb
Johannes Groß:
Hi,
while generating henshin rules from an EMF based UML
model, i am asking myself how to treat references
(eReferences) to the rest of the model.
So say i have an instance specification in my LHS and RHS
that has a classifier, do i need to model this classifier in
the rule as a node or is there a way to reference it as an
"outside element"?
Thanks,
Johannes
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/henshin-dev
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/henshin-dev