I observed a behviour in EA14.0 that has been changed from the behaviour in EA12.5.
Summary
In EA12.5 when using a Deployment Specification
one had to set the Instance Classifier
on the Deployment Specification
object in order to be able to set the run state (Ctrl+Shift+R
). It was not necessary to set a Parent
on the object. In EA14.0 one has to specify a Parent
from which the attributes are derived that can be overridden, and I addtion the Instance Classifier
has to be set but it can be set to an arbitrary object (not related to the Parent
).
In the following sections I outlined the steps I executed:
Setting a run state in EA12.5
Result of a
Deployment Specification
As we can see the actualInstance Classifier
class is visible on theDeployment Specification
object. It serves as the basis from which theVariables
can be configured.
Setting attribute initializers in EA14.0
When trying the same steps in EA14.0 I get the following error message:
However, when I additionally specify a
Parent
on theDeployment Specification
object I can configure the variables defined theParent
class.In this case it does not matter which
Instance Classifier
I specified. In the following figure I set theInstance Classifier
to an empty class calledTotally unrelated object
(with not attributes defined).Side note: when I open a model/EAP-file created in EA12.5 in EA14.0 I can still see the previously configured run states, but am not able to any more modify them (unless I set the previously assigned
Instance Classifier
to theParent
).
Questions
So this seems to be a breaking change to me and my (multipart) question is:
- Am I doing something wrong?
- Does anyone know anything about this changed behaviour and the possible rationale behind it?
- Does anyone know an easy trick how I can migrate all my existing
Deployment Specification
objects in my multiple models?
Thank you for your answers and suggestions!
Regards, Ronald