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

Bug 348653

Summary:	[Model Explorer] Some "move" in the model explorer should be forbidden
Product:	[Modeling] Papyrus	Reporter:	Yann Tanguy <yann.tanguy>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	vincent.hemery
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:
Bug Blocks:	355731

Description Yann Tanguy

2011-06-07 17:43:39 EDT

It may be a good option to make some "creation verification" before allowing to move elements.

For example if the creation of a FlowProperty is only allowed on FlowSpecification, there is no reason to allow to move such element on any other kind of elements (ex: an Enumeration).
Currently the default policy is "always allow" to move elements (if allow by UML2 EMF implementation). It may be better to choose the opposite policy "Always forbid" and make exception where an implementation is provided, or behavior has been validated.

Comment 1 Ansgar Radermacher

2013-03-19 06:04:34 EDT

This can be reproduced with 0.10.X. I don't think that we should prevent to move a flow property to an interface that is not stereotyped as FlowSpecification, since the user might want to add the FlowSpecification stereotype to the latter or remove the FlowPropery stereotype from the former. This should perhaps be part of model validation rules.
However, it should not be possible to move a property into an enumeration, as we don't allow the creation of a property within an enumeration (even if the latter is technically a classifier).