Consider the case where a derived feature is annotated with OCL to provide the\
required value. Currently, the use of such derived features (or operation\
bodies) makes working with dynamic instances impossible, as code generation\
from dynamic templates is required in order for the feature to be accessed by a\
QVT transformation that uses it.
Provided, there is a standard way to add OCL annotations for derived features and operation bodies, they can be recognized in the .ecore model and evaluated on dynamic instances loaded from the workspace.
| --- | --- | | Bugzilla Link | 208598 | | Status | RESOLVED FIXED | | Importance | P3 enhancement | | Reported | Nov 02, 2007 13:56 EDT | | Modified | Nov 02, 2007 16:05 EDT | | Reporter | Radomil Dvorak |
Description
Consider the case where a derived feature is annotated with OCL to provide the\ required value. Currently, the use of such derived features (or operation\ bodies) makes working with dynamic instances impossible, as code generation\ from dynamic templates is required in order for the feature to be accessed by a\ QVT transformation that uses it.
Provided, there is a standard way to add OCL annotations for derived features and operation bodies, they can be recognized in the .ecore model and evaluated on dynamic instances loaded from the workspace.