OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Using entity name in implementation scripts


Regarding both 1.3 and draft 2.0, there is no method for the mandatory name of a modelable entity (e.g., Node Template or Relationship Template name) as declared in the service template to be referenced by an implementation script associated with that entity.
This is because the get_property function defines <property_name> as mandatory which must be a property name.

Note that this situation is in contrast to Relationship templates which do have access to the mandatory node template names at each end via the TARGET and SOURCE variables.

My current work-around is to define a property in the Node Template which is given a value equal to the node template name. This is not ideal as it may inadvertently be set to the wrong value and thus not match a test with the value TARGET and SOURCE.

A potential enhancement would be to allow <property_name> to optionally be a new reserved work such as SELF_NAME

Regards

Paul Jordan




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]