Summary
When a Component Implementation is instantiated,
The corresponding system Instance (the root of the generated Instance model) has 2 properties:
- Component Implementation (specific to System Instances, not available in Component Instances)
- Classifier
Actual behavior
During Instantiation, the Component Implementation property is populated, but not the Classifier property (which should have the same value as the Component Implementation property).
Expected behavior
The Classifier property should also be populated with the same value as that of the Component Implementation property.
Desktop (please complete the following information):
- OSATE Version: 2.10
- Operating System: Linux
Additional context
One question to ask is : why is there a different 'Component Implementation' property in the first place?
One reason I can think of is that OSATE allows instantiation of components other than system. So maybe this has something to do with that
Summary
When a Component Implementation is instantiated,
The corresponding system Instance (the root of the generated Instance model) has 2 properties:
Actual behavior
During Instantiation, the Component Implementation property is populated, but not the Classifier property (which should have the same value as the Component Implementation property).
Expected behavior
The Classifier property should also be populated with the same value as that of the Component Implementation property.
Desktop (please complete the following information):
Additional context
One question to ask is : why is there a different 'Component Implementation' property in the first place?
One reason I can think of is that OSATE allows instantiation of components other than system. So maybe this has something to do with that