-
Notifications
You must be signed in to change notification settings - Fork 8
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
Null pointer exception in end to end flow instantiation #2287
Comments
In OSATE 2.7.1 exceptions during instantiation are properly reported. This model results in an NPE during flow instantiation.
|
When I instantiate
Now, of course, is the question of why do we get this. |
This caused by the refinement of the flow specification. The refined model object doesn't have the data we need. We need to climb up to the original non-refined flow specification. I'm not sure if this problem is going to come up in another spot in this code. |
Exception comes from This is called by
I think these are the only spots where this would be a problem. |
Easy to fix, I think. Just replace |
That seems to fix things. Need to add unit test |
Fixed. Added test. |
Summary
When I instantiate System Impl Example.Low in the attached model, a popup appears with subject message. There are no error markers on the model before instantiation. No other errors appear as markers or in the Problems tab. This behavior repeats after repeated project cleans.
Expected and Current Behavior
I would expect it to either instantiate without the popup notice or issue a more informative error message with markers on the instance file or AADL model.
Steps to Reproduce
Model attached
Environment
The text was updated successfully, but these errors were encountered: