Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Classifier property of the root element in an Instance model is not populated during instantiation #2823

Closed
raks0009 opened this issue Jul 7, 2022 · 0 comments · Fixed by #2827

Comments

@raks0009
Copy link

raks0009 commented Jul 7, 2022

Summary
When a Component Implementation is instantiated,
The corresponding system Instance (the root of the generated Instance model) has 2 properties:

  1. Component Implementation (specific to System Instances, not available in Component Instances)
  2. 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

@lwrage lwrage self-assigned this Jul 8, 2022
@lwrage lwrage added this to the 2.12.0 milestone Jul 8, 2022
@lwrage lwrage changed the title Classifier property of the root element in an Instance model is not populated during insantiation Classifier property of the root element in an Instance model is not populated during instantiation Aug 1, 2022
lwrage added a commit that referenced this issue Aug 1, 2022
@lwrage lwrage mentioned this issue Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants