Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327342

Summary:	[Properties view] Selection of specification (of a method) shows a list with too many choices and without namespace qualification
Product:	[Modeling] Papyrus	Reporter:	Ansgar Radermacher <ansgar.radermacher>
Component:	Views	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	rschnekenburger
Version:	0.10.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Ansgar Radermacher

2010-10-08 10:26:18 EDT

If the user has wants to assign a specification to a method, the opened dialog presents all operations (BehavioralFeatures) of a model. However, UML 2.3 states in section "13.3.2 Behavior" that the referenced behavioral feature must be either owned or inherited:

• specification: BehavioralFeature [0..1]
Designates a behavioral feature that the behavior implements. The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it. The parameters of the behavioral feature and the implementing behavior must match. A behavior does not need to have a specification, in which case it either is the classifier behavior of a BehavioredClassifier or it is a behavior that can only invoked by another behavior of the classifier.

Thus, the available choice is larger than the subset allowed by UML. It is quite difficult to select the right operation since the owning class is currently not shown and many operations of different classes could have the same name (e.g. due to classes implementing standard interfaces).

Comment 1 Camille Letavernier

2013-05-06 14:24:47 EDT

This is a general issue in the Properties view, where references are filtered by (meta)type, and not by context.

The same problem occurs for e.g. "Subsetted properties" and many others.