- changed milestone to MODELS 2014 Demo
Add postprocessing step to structural weaver to update referenced elements
Steps to reproduce:
- Create AspectA with Class A
- Create AspectB with Class B
- Extend AspectA
- Create operation "+ A getA()" in Class B
- Weave
Result:
The return type referring to A in the operation is not updated in the woven aspect, it points to A in AspectA. This can be observed by the validator (there is an error) and when saving the model.
Currently, existing elements are not updated. I think this requires an additional post-processing step to take care of it.
Comments (7)
-
reporter -
reporter -
assigned issue to
- edited description
This should be done once issue
#161is resolved (improvements toReferenceUpdater
).The following classes need to be updated:
- ClassifierMapping (to element could be from extended aspect)
- Operation (return type)
- Attribute (type)
- Parameter (type)
-
assigned issue to
-
reporter References issue
#160: Added reference updating for parameter (type), operation (return type) and classifier mapping (to element).→ <<cset 070564565279>>
-
reporter -
assigned issue to
-
assigned issue to
-
reporter References issue
#160: Added reference updating for OperationMapping and ParameterMapping.Fix for updating list of objects to be able to call it passing a list of any sub-class of EObject.
→ <<cset b22f90454eb5>>
-
reporter References issue
#160: Introcuded postprocessing operation to PostProcessor, which then internally performs the required postprocessing steps.Added postprocessing step to update the references of the woven aspect (higher-level) using the ReferenceUpdater.
The updating of references in the updateInstantiationDeclaratives step (addressed in issue
#58) is now handled by ReferenceUpdater in the second postprocessing step.→ <<cset 97b5484b806f>>
-
reporter - changed status to resolved
- Log in to comment