From time to time I stumble over scripts like the following:
child.getProfilePropertyValue('myProperty')[0];While this is perfectly fine for OCL scripts, it is not ideal for JavaScript based scripts. OCL was merely the first scripting language that was implemented in medini, mainly to write constraints. The OCL implementation is strong typed and is working solely on the predefined EMF metamodel - only attributes and operations from the metamodel can be called / accessed. To access dynamic attributes (and that is what the project specific profile properties are) the operation "getProfilePropertyValue" was introduced.
For JavaScript as a lose typed language the binding to EMF is less strict. Consequently we were able to dynamically map access to attributes also to profiles. So the above script can be shortened to:
child.myProperty
To summarize: simply access profile properties the same as predefined attributes.
Happy scripting
Jan
