| Re: [henshin-dev] Debugging dangling edges |
Hi Christian,
Thanks for the answer. For practical purposes, setting the flag to false should solve the problem.
I was reluctant to do this so far because (1) I think in some cases it may leave the target model in an inconsistent state by deleting a required EReference
(though now I realize this cannot happen in my case) and (2) I was not aware that setting the flag to false will lead to the interpreter deleting these edges, rather than just ignoring them.
Cheers,
Vlad
From: henshin-dev-bounces@xxxxxxxxxxx [mailto:henshin-dev-bounces@xxxxxxxxxxx]
On Behalf Of Christian Krause
Sent: Wednesday, November 05, 2014 1:57 PM
To: Henshin developers mailing list
Subject: Re: [henshin-dev] Debugging dangling edges
Hi Vlad,
if you set the check dangling flag to false, the interpreter will automatically delete all dangling edges (under the premise that all referencing objects are part of the EGraph). Does this solve your issue?
Cheers,
Christian
2014-11-05 10:21 GMT+01:00 Vlad Acretoaie <rvac@xxxxxx>:
Hi,
This is a problem I am running into constantly when transforming models conforming to large and complex metamodels (e.g. UML): when deleting a model element, a dangling edge appears
in the target model, and the transformation fails (assuming that the Check Dangling Edges flag is set to true).
Because of the size of UML, it often takes me a long time to figure out exactly which dangling edge I have created, so that I can explicitly delete it in my transformation. Is there
any way to get this information from Henshin? Getting the name of the offending EReference would be sufficient.
Cheers,
Vlad
|
||||||||||||||||||||
_______________________________________________
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