Bug 473140 - [NewChild] New Relationship menu cannot create association between UseCase and Actor
Summary: [NewChild] New Relationship menu cannot create association between UseCase an...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 1.1.0   Edit
Hardware: PC Mac OS X
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-21 04:12 EDT by Christian Damus CLA
Modified: 2020-01-29 11:02 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Damus CLA 2015-07-21 04:12:54 EDT
Papyrus Mars

In the Model Explorer, the "New Relationship -> Association" action does not work for use cases and actors.

Steps to reproduce:

1. Create a Use Case diagram.
2. Create a use case and an actor in the diagram.
3. In the Model Explorer, select the use case.
4. Invoke the "New Relationship -> Association" action in the context menu.
5. In the ensuing dialog, choose the actor as the target element.
   ==> Observe that the selection is not accepted:  the OK button is disabled.
Comment 1 Olivier Cailloux CLA 2020-01-29 11:02:52 EST
The problem still exists with Papyrus installed on Eclipse version 2019-12 (4.14.0).

To be more complete, selecting a Use Case or an Actor in the Model Explorer, then New Relationship, then Association does not let you choose anything in the ensuing “Target Element Selection” dialog: no possible target appears (not even the root model element, which should appear in the Tree view of that dialog), as if the model was empty. Thus, the action can’t be completed.

Selecting a Class or an Interaction in the Model Explorer, then New Relationship, then Association works as expected: the Target Element Selection dialog shows other elements as possible choices and accepts (for example) that I choose a Use Case as a target. The corresponding Association then appears in the Model Explorer as a child of the selected Class or Interaction.