Re: [henshin-dev] Henshin-rules and BPMN2-Models

[Stefan Jurack <henshin.stj@xxxxxxxxx>]

Hi Jens,

I did not take a closer look into your scenario. However, what you describe sounds like dangling case. That means, the deletion of a node may only take place if and only if there is no dangling edge left behind.

So in your case, if preserved, the "Task" node is matched as you expected. But since there seems to be at least of edge being connect to/with this node, the previously found "Task" node is no valid match here.

Might this be the reason?


Regards,
Stefan




Am 28.10.2012 16:33, schrieb Jens Bürger:

Hello everyone,

I am trying to do model transformation on BPMN2-models at the moment.
I managed loading a BPMN2-Model modelled with BPMN2 Modeler.

I've modelled a very simple process and, as a first step, want to delete a certain task.

While Henshin finds a match for my rule when the node "Task" is typed <<preserve>>, it does not so when typed <<delete>>.

I'm a little bit confused why this seems to make such a difference?

I attached all relevant files to this mail so you can have a look at it.

Thanks in advance,

Jens

_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev