Community
Participate
Working Groups
Created attachment 264539 [details] Example legacy model that highlights the issue If you import a legacy model, then no port labels are shown, neither for ports of the capsule, nor for ports on capsule parts. Steps to reproduce: 1) Import the attached model 2) Check the three capsule structure diagrams after import 3) Observe how no port labels are shown, neither for capsules nor for capsule parts For comparison I will attach some screen shots how the diagrams looks like in the legacy tooling.
Created attachment 264540 [details] Screen shot of structure diagram for Top in legacy tooling
Created attachment 264541 [details] Screen shot of structure diagram for Capsule1 in legacy tooling
Created attachment 264542 [details] Screen shot of structure diagram for Capsule2 in legacy tooling
As can be seen from the screen shot, other layout issues can also be seen, e.g. that the legacy SAP on capsule parts are "disconnected" from the border of the capsule part and that the connectors gets additional bend-points compared to the original diagram. But those I guess we should track with separate Bugzillas if needed.
This issue should be solved in the Papyrus migration extra plugin. I created Bug 507860 to track the Papyrus fix
(In reply to smaoui asma from comment #5) > This issue should be solved in the Papyrus migration extra plugin. I created > Bug 507860 to track the Papyrus fix Could you please rename that other Bug 507860? It is so confusing when two bugs (one depending on the other) have exactly the same name.
Verified to be fixed in the latest Papyrus-RT build, based on the latest Papyrus build. The ports in capsule structure diagrams do now have their labels as expected. There are still a few aspects that can be seen with the example model attached to this bug, e.g how the legacy SAP and SPP (with wrong setting of service) is handled, and also how visibility of the ports are not set according to the migration notes in the UML-RT profile document, i.e. ports with isService=true shall have visibility=public and isService=false shall have visibility=protected. These issues shall be tracked with separate bugs. Putting this bug though into verified fixed.
Closing as verified fixed.
