Skip to content
This repository was archived by the owner on May 17, 2018. It is now read-only.

Capability to Correct Broken References to the AADL Model #136

Closed
philip-alldredge opened this issue Oct 6, 2015 · 1 comment
Closed
Milestone

Comments

@philip-alldredge
Copy link
Contributor

philip-alldredge commented Oct 6, 2015

capability to correct broken references to the AADL model.

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.

@philip-alldredge philip-alldredge added this to the 2016-09 milestone Oct 6, 2015
@philip-alldredge philip-alldredge changed the title Improve Handling with Model Element isn't Retrieved. Improve Handling when Model Element isn't Retrieved. Oct 14, 2015
@philip-alldredge philip-alldredge modified the milestones: 2016-09, Next Iteration Planning May 4, 2016
@philip-alldredge philip-alldredge modified the milestones: Next Iteration Planning, Planning (Threshold) Feb 24, 2017
@philip-alldredge philip-alldredge changed the title Improve Handling when Model Element isn't Retrieved. Improve Handling of Broken References. Feb 26, 2017
@philip-alldredge philip-alldredge modified the milestones: Planning, Enhancements R2 Jul 10, 2017
@philip-alldredge philip-alldredge changed the title Improve Handling of Broken References. Capability to Correct Broken References to the AADL Model Jul 10, 2017
@philip-alldredge
Copy link
Contributor Author

philip-alldredge commented Oct 13, 2017

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.

philip-alldredge added a commit that referenced this issue Dec 8, 2017
Adds option to adjust diagram context when opening diagram if the
diagram's context cannot be bound.

Adds option to restore ghosted diagram elements.

Closes #136.
RyanMcilnay pushed a commit that referenced this issue Dec 11, 2017
Adds option to adjust diagram context when opening diagram if the
diagram's context cannot be bound.

Adds option to restore ghosted diagram elements.

Closes #136.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant