| Re: [henshin-dev] Using predefined UML primitive types in Henshin |
Hi Thorsten,
Thank you for the explanation. The situation is much clearer to me now – I was confused by the availability of the String type in the “Choose Node Type and Action” dialog.
Cheers,
Vlad
From: henshin-dev-bounces@xxxxxxxxxxx [mailto:henshin-dev-bounces@xxxxxxxxxxx] On Behalf Of Thorsten Arendt
Sent: Tuesday, May 06, 2014 2:46 PM
To: henshin-dev@xxxxxxxxxxx
Subject: Re: [henshin-dev] Using predefined UML primitive types in Henshin
Hi Vlad.
As a workaround, I could add a node of type PrimitiveType and set its name property to “String”, but I am curious if I can use the actual String type in UML and not define my own.
This is not an own defined PrimitiveType of name 'String'; it is indeed the one defined in the UML library. Take a look to the attached example (you find it in directory 'files140506'). Here, the rule owns a preserved node of Type PrimitiveType with name 'String'. This rule only matched if the corresponding UML model already imports the PrimitiveType library, i.e., there is already a PrimitiveType named 'String'.
However, the UML primitive types are modeled as instances of meta type 'EDataType'. IMO the type of a Henshin node must be an EClass of the corresponding meta model. Therefore, a node can not be of type 'String' (since it is NOT modeled as EClass). Maybe the dialog 'Choose Node Type and Action' does not distinguish between EClass and EDataType (then, this is a bug).
Regards,
Thorsten--
Dipl. Inf. Thorsten Arendt
Philipps-Universität Marburg
Fachbereich Mathematik und Informatik
Hans-Meerwein-Str.
D-35032 Marburg
Office: 05D18
Phone : +49-6421-2821540
Email : arendt@xxxxxxxxxxxxxxxxxxxxxxxxx
--
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev