philip-alldredge
commented
7 years ago Additional Thoughts
- Handling Errors When Finding Business Object Context
- Seems to occur if there was an exception during load previously.
- Handle case where an element no longer exists. Need to allow relinking ghosts elements.
- One such case is that an implementation is renamed to implement a different type.
- Being able to convert a reference to a label would be helpful for the UI in this case.
- Project Clean while in graphical editor triggers unable to find context exception?
- A project clean/build while the editor is displaying an unable to find context exception does not cause the editor to start working. User must close and reopen editor.
- Unable to find context exception should be handled in a better manner. Should trigger an auto recovery and then UI for user options if that fails.
- Ensure that errors are displayed to the user when they occur. Some errors which occur in non-UI threads are simply written to the log.
Need the capability to correct broken reference to the AADL model. With the referencing changes, these problems should occur less frequently but may still occur. Need to handle both intermittent and permanent model element retrieval/referencing issues. Prompt user to optionally select a new context configuration and other business objects if can't be found. If it isn't the context business object, then will need to decide how to prompt the user. Don't want to annoy the user and there are plenty of cases where business objects will be removed under normal operation.