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

Error states with error types should not be triggered by error events without types or non-matching types #2125

Closed
reteprelief opened this issue Dec 19, 2019 · 0 comments · Fixed by #2138
Assignees
Milestone

Comments

@reteprelief
Copy link
Contributor

@reteprelief reteprelief commented Dec 19, 2019

Error states can be defined to be error type specific, i.e., they carry an error type from a specified list of allowable types.
Either the type is explicitly specified in the target state specification, or the target state specification is without type. In that case the error type of the error event is used. In that case the error type of the error event must be contained in the set of error type specified with the state. Furthermore, an error event without a type cannot trigger the transition if the target state is expected to carry a type.

OSATE should provide a validation to inform the user of this issue. Furthermore, the fault trace/tree generation should not include an error event that cannot trigger the state carrying types.

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.

1 participant