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

Bug 343104

Summary:	[General][Classifier behavior] When user create a new behavior Diagram, the classifier behavior is always changed
Product:	[Modeling] Papyrus	Reporter:	Fabien Gautreault <fabien.gautreault.ext>
Component:	Diagram	Assignee:	Ansgar Radermacher <ansgar.radermacher>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	raphael.faudou, samuel.rochet
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Fabien Gautreault

2011-04-18 04:21:31 EDT

Build Identifier: 20100617-1415

[General][Classifier behavior] When user clic on an element on the outline and create a new behavior Diagram, the classifier behavior is always changed. For example create a new Activity diagram will put an activity0 as classifier behavior, and create another Activity diagram will put the activity1 as classifier behavior. The classifier behavior shouldn't be changed or at least ask user if he wants to. It seems that all classifiers are acting like this.

Reproducible: Always

Steps to Reproduce:
1.Select an element in the outline
2.Clic right => Create Diagram => "Behavior diagram". As a result the classifier behavior own the classifier representing the diagram, such as an activity0 for an Activity diagram
3.Clic right => Create Diagram => "Behavior diagram". As a result the classifier changed again.

Comment 1 Sébastien Gérard

2013-03-28 05:02:28 EDT

This bug is still reproductible. Behavior to implement is to set the behaviorClassifier attribute when creating a behavior in the context of a BehavioredClassifier such as a class.

Comment 2 Ansgar Radermacher

2013-04-11 04:43:25 EDT

The proposed solution is not clear. The user can create a state-machine diagram in the context of a class first and then add an activity diagram in the context of the same class. As a result, the classifier behavior will change when the user adds the activity diagram.
I think, a valid solution would be to warn the user during creation of a new contextual diagram if the classifierBehavior is already set.

Comment 3 Raphael Faudou

2013-04-11 06:38:06 EDT

Good solution.
+1

Comment 4 Sébastien Gérard

2013-04-15 16:35:24 EDT

*** Bug 405571 has been marked as a duplicate of this bug. ***

Comment 5 Ansgar Radermacher

2013-06-12 03:43:31 EDT

Fixed in r11452