Re: [henshin-dev] Henshin Search Pattern Problem

[Juergen Freund <freund@xxxxxxxxxxxxxxxxxxxx>]

Hi all,

thank you for your replies.

The rule I sent you which was not working for me is actually a part of a much more complex rule which was auto generated.

But indeed I fixed this generation algorithm a bit and could replace the required nodes with preserved ones and then my rules were working flawlessly again.

So at the moment this has not to be disabled for me. But thanks anyway.

Unfortunately I have no fix for that problem since I did not completely understand the underlying code and had not much time yet to analyze it in detail.

Greets,
Jürgen

Dipl.-Ing. Jürgen Freund
Arbeitsgruppe Ähnlichkeitsmechanik

Telefon: +49 (0)711 685 69530
E-Mail:  freund@xxxxxxxxxxxxxxxxxxxx

Postadresse:
Universität Stuttgart
Institut für Statik und Dynamik der Luft- und Raumfahrtkonstruktionen
Pfaffenwaldring 27 - Zimmer 01.002
70569 Stuttgart

On 16.12.2015 13:19, Christian Krause wrote:

Hi all,

this could be a bug. Currently I don't have time to look into it. If you know a solution, please push a change. ALternatively, we could (temporarily) disable the path constraints.

Cheers,

Christian

2015-12-16 10:31 GMT+01:00 Matthias Tichy <matthias.tichy@xxxxxxxxxx>:

hi,

I again have a little problem with the Henshin transformation engine.

I constructed a search pattern which leads the engine to a
NullPointerException. I could track down the error to its cause but I am
not really sure why this happens.

I attached a picture describing the Search pattern (Rule reconstruct)
which causes the error and I also attached a full example project
causing this error.

Any help is really appreciated and I would be happy to hear something
from anyone about this.

I just did some debugging.

The problem is related to the automatic generation of Path constraints when required nodes (=PACs) are used. This automatic generation of path constraints is a performance improvement. It seems that your rule has the specific case that there is an edge between a required node in the PAC of the multi rule and a preserve node in the kernel rule.


@Christian: In Path.java:104, mappings are searched for the source of the edge but there exists no mapping because it is a PAC. This seems to be a bug. is it?


As a workaround, i changed in your henshin-rule the required node to a normal preserve node and then your example was executed.

Greetings to Stuttgart,

Matthias


--
Prof. Dr. Matthias Tichy
Institute of Software Engineering and Compiler Construction
Faculty of Engineering, Computer Science and Psychology
University of Ulm
89069 Ulm, Germany

Tel.:  +49 731 50-24160
Fax:   +49 731 50-24162
email: matthias.tichy@xxxxxxxxxx


_______________________________________________
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