Hi, Peter, Bran,
Indeed, the Eclipse UML2 implementation predates any ability that we had either to execute embedded OCL constraints or to translate them to Java automatically, so the subset of the UML metamodel constraints that are specified in the model as OCL that were actually implemented were done “by hand”.
So, the reason why the legacy tooling works as one expects is that it is (still) based on a version of the UML specification before it (apparently) regressed. And, of course, the Eclipse UML2 project faithfully implemented that regression.
So, since we are agreed on Option 2, then I am happy to say that that is what already was implemented before I raised this question, so we are good to go. Thanks, all, for this helpful discussion!
I shall raise a bug for Eclipse UML2 to raise an OMG issue and, if they wish to, preemptively fix this state machine constraint.
On Mar 6, 2017, 08:35 -0500, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:
Hi,
Some comments inline below.
/Peter Cigéhn