Avoid missing and duplicated IDs
The console displays a lot of warnings regarding missing or duplicated IDs:
!MESSAGE The following missing/duplicate IDs have been fixed in "AF3-Project3.af3_23".
Please report this incident since it indicates a programming error that could result in corrupted model files.
Duplicate ID 9 disambiguated for element "org.fortiss.af3.safety.model.annotation.impl.SafetyIntegrityLevelImpl@3e9053b3 (id: 9, name: null) (safetyStandard: undefined, asilValue: QM, dalValue: DAL E, silValue: SIL0, undefinedStandardValue: <unset>)"
Missing ID added to element "org.fortiss.af3.safety.model.annotation.impl.SafetyIntegrityLevelImpl@4b45016d (id: 0, name: null) (safetyStandard: undefined, asilValue: QM, dalValue: DAL E, silValue: SIL0, undefinedStandardValue: <unset>)"
Steps to reproduce
- New Project
- Add new CA
- Add two components
- Save project
Furthermore, similar tests should be preformed with other model elements that carry annotations (e.g., task architecture, allocations, …)
AF3 Features that rely on IDs
- Model persistence
- Description: Model elements are referred by ID
- Entry point: org.fortiss.tooling.kernel.internal.storage.eclipse.ModelContext.doSave()
- Code generation
- Description:
- Entry point:
- NuSMV
- Description:
- Entry point:
- DSE (Z3)
- Description:
- Entry point:
- ??
- Description:
- Entry point:
(from redmine: issue id 3642, created on 2019-02-18)
- Uploads:
- Migrate_Execution_Configuration.af3_23 Test case for deprecation of IIdLabledReference