Bug 511627 - [Tooling] Selecting a new protocol for a port does not allow selection of system protocols in run-time model library
Summary: [Tooling] Selecting a new protocol for a port does not allow selection of sys...
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-03 06:57 EST by Peter Cigehn CLA
Modified: 2017-02-03 08:13 EST (History)
3 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 2017-02-03 06:57:47 EST
If you use the three dots ... button next to the Protocol property of a port, to select a another protocol for an existing port, then the browse dialog does not display the system protocols in the run-time model library. It do however show the base protocol, UMLRTBaseCommProtocol, which preferably should *not* be available for selection (since it does not really make sense to have a port directly typed by this base protocol).

Steps to reproduce:

1) Create a new UML-RT model based on the "UML-RT for C++" template
2) Create a capsule in this model
3) Open the structure diagram and create a port using the port tool on the palette. Select the Timing protocol directly from the popup menu.
4) Select the port
5) Open the properties and press the ... button next to the protocol property field
6) A browse dialog appears.
7) Observe how the <<ModelLibrary>> UMLRT-RTS is shown, but it is empty, apart from the nested Internal package. You can browse into the Internal package and see/select the <<Protocol, BaseProtocol>> UMLRTBaseCommProtocol (which does not really make sense), but you cannot see any of the three system protocols in the root of the UMLRT-RTS library (Log, Timing, Frame) as expected.