Multiple Platform Architectures not Supported in Deployment Mapping
If an AF3 Component Architecure has already been mapped via a Deployment to a Platform Architecture, the definition of a second mapping via drag/drop for an alternative Platform Architecture is not possible in the Component-ECU-Mapping View.
In the Raw Mappings Pane, the definition of a new assignment does not work, because the secdond alternative Platform Architecture is not offered in the dialog (even it is already selected in the ECU-Component-Mapping view).
#3 Updated by Florian Hölzl almost 8 years ago
- Status changed from New to Feedback
- Assignee changed from Florian Hölzl to Bernhard Schätz
Please clarify the problematic case:
a) the problem occurs with a second deployment (using the same LA, but a different PA) in the same model
b) the problem occurs when changing in a given deployment from one PA to another
c) the intention was to use one LA with two PAs in a single deployment (i.e. two components go to PA_1 and three others to PA_2).
#6 Updated by Florian Hölzl almost 8 years ago
- Status changed from Feedback to In Progress
- Assignee changed from Florian Hölzl to Anonymous
- % Done changed from 0 to 70
Bug was fixed, by changing several methods in af.deployment.util.DeploymentUtils.
Several methods have been deprecated and replaced with equivalent methods, which have the deployment object as an additional parameter.
The deprecated methods are still used in
Please check these implementations and change them if possible.