[henshin-dev] info: OCL constraint support for our Henshin metamodel has

[Stefan Jurack <henshin.stj@xxxxxxxxx>]

 Servuz guys,

I just have completed the extension announced earlier: In addition to an
ordinary OCL constraint, an individual message text and a severity
may(!) be deposited. Such a case can be found, e.g., in element
"NamedElement".
In the following some details are given on that:

1a) The message text has to be part of the same OCL Annotation and
requires a key composed by the key of its referring constraints, e.g.
"ValidName", and the string ".Msg": "ValidName.Msg". Capitalization matters!
1b) The value of this entry may be either the message directly or
otherwise a pointer to the plugin.properties. For the latter case the
value is required to start with an underscore character, e.g.
"_Ocl_Msg_NamedElement_ValidName" while in plugin.properties a
corresponding key/value pair has to exists, e.g.
"_Ocl_Msg_NamedElement_ValidName=If a name for an entity is set, the
name must not ...."

2a) The severity may be given analog to (1a): "ValidName.Severity".
Capitalization matters!
2b) The value of this entry may be either "info", "warning" or "error".
Capitalization does not matter here.
2c) The default value for severity is "error".

Let's start to implement some meaningful constraints. ;-)

greetx, Stefan

Attachment: signature.asc
Description: OpenPGP digital signature