Bug 502385 - [Tooling] Renaming a protocol using F2 only renames the internal collaboration
Summary: [Tooling] Renaming a protocol using F2 only renames the internal collaboration
Status: CLOSED FIXED
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.7.2   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: 0.9.0   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 506896
Blocks:
  Show dependency tree
 
Reported: 2016-09-28 04:41 EDT by Peter Cigehn CLA
Modified: 2016-11-08 08:10 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cigehn CLA 2016-09-28 04:41:43 EDT
If you rename a protocol using F2, then this only renames the actual collaboration of the protocol. The other internal elements, i.e. the <<ProtocolContainer>> Package and the three <<RTMessageSet>> Interfaces does not get renamed according to the naming rules for the internal elements of a protocol.

Steps to reproduce:

1) Create a UML-RT model
2) Create a protocol in this model
3) Press F2 to bring up the dialog to rename the element
4) Give the protocol a new name
5) Save the model
6) Open the .uml-file directly in the UML model editor
7) Observe how the <<ProtocolContainer>> Package and the three <<RTMessageSet>> Interfaces still have their old names, and only the <<Protocol>> Collaboration have gotten the new name.

It must be ensured that the internal elements of a protocol gets renamed correctly, disregarding in which way the protocol is renamed, e.g. using F2, using the properties view.

This is guess also highly related to the functionality to be able to edit the name "inline" in the model editor, which will also be possible to trigger using the F2 and replace the modal dialog that pops up. See Bug 492356.
Comment 1 Christian Damus CLA 2016-11-03 11:32:51 EDT
The fix for blocking bug 506895 is available in the latest Papyrus Neon.2 nightly builds.
Comment 2 Peter Cigehn CLA 2016-11-08 08:10:28 EST
I have verified this in the latest Papyrus-RT build. All the internal elements of the protocol (<<ProtocolContainer>> Package, <<Protocol>> Collaboration and the three <<RTMessageSet>> Interfaces) gets renamed according to their naming rules when using F2.
Comment 3 Peter Cigehn CLA 2016-11-08 08:10:47 EST
Closing as verified fixed.