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

[Christian Krause <henshin.ck@xxxxxxxxx>]

Hi Jens,

it could be a reference to the container object. If you want to create or delete an object, you should always explicitly add /delete it to/from its container object. In your case, this should be an instance of Process.

You have 2 options:

1) explicitly add a Process node in your rule (type <<preserve>>) and add edges (at least) to the objects that you want to delete (and create).

2) the graphical editor supports some syntactic sugar for such cases: in the label of the rule, write "bpmntest @Process". This should automatically add a "transparent" container object for you. You can see the effect in the tree-based editor. You should see a new object root:Process and containment edges to all other nodes. See also this wiki page:

http://wiki.eclipse.org/Henshin_Graphical_Editor#Parameters_and_Transparent_Containers

Cheers,
Christian


On 10/29/2012 01:52 PM, Jens Bürger wrote:

Am 28.10.2012 16:46, schrieb Stefan Jurack:
[...]

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?

I'm not really sure.

In first case, it is: when setting "checkDangling" to false the transformation works.

The only model objects that may be connected to the Task may be "Sequence Flow"-objects. So I modelled them to into the Henshin rule.
But again: when "checkDangling" is true, the transformation is not performed.

I removed the BPMN-Diagram-data from the file and "forced" the transformation with "checkDangling" set to false.

I attach a screenshot of the altered rule and the BPMN2-Model before and after the transformation. I do not really see where the transformation leaves "dangling edges" left (?)

Thanks in advance,

Jens

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