|Implementation of (all) constraints - is it intended? [message #692808]
||Tue, 05 July 2011 05:25
| Kirsten M. Z.
Registered: July 2010
I have a simple question: is there the intention to implement all constraints which can be found in the UML meta model? I saw that most constraints are defined according to the UML 2.x specification. Or rather, there are unimplemented constraints which have a documentation showing the OCL constraint from the UML specification. For example, an initial pseudostate may only have one outgoing transition. So the constraint is defined, documented, but the (generated) code has no implemented validation (Indigo release).
On the other hand, many other constraints are implemented (e.g. no two named elements with the same qualified name).
Therefore, I want to ask if there is a special reason why some constraints are not implemented, e.g. it would break old models which did not care about meticulous constraints, or too many implementations would interfere further development, it would become too slow, etc.
Or as alternative: generating code from the annotated OCL.
Maybe it is implemented already, but I have to use another branch/code generation?