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

Bug 329353

Summary:	[Profile Diagram] Drop Dependency with an Association as client or supplier throws Exception
Product:	[Modeling] Papyrus	Reporter:	Vincent Lorenzo <vincent.lorenzo>
Component:	Core	Assignee:	Patrick Tessier <Patrick.Tessier>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3
Version:	0.7.0
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	329346

Description Vincent Lorenzo

2010-11-03 10:27:02 EDT

Steps to Reproduce : 
	1/ Create 2 Stereotypes, ste1 and ste2 with an Association between them
	2/ Create an other Stereotype ste3
	3/ Create a Dependency between ste3 and the Association
	4/ Try to drop the Dependency
		-> You get an Exception
Note : this bug exists in the Class Diagram also.

Comment 1 Vincent Lorenzo

2010-11-03 10:31:30 EDT

The ends of a Dependency are NamedElement. Tests in the Class Diagram show that the drop of a Dependency throw an Exception, when a end is not a Node.

Comment 2 Vincent Lorenzo

2010-11-03 11:58:49 EDT

We get an NPE, because, the EditPart for the source/target is AssociationNameEditPart and not AssociationEditPart. The problem comes from CommonDeferredCreateConnectionViewCommand.

Comment 3 Vincent Lorenzo

2010-11-04 04:29:55 EDT

Done in r3110.

Comment 4 Patrick Tessier

2011-05-19 05:34:54 EDT

dependency and mutli-dependency must not be designed in the profile diagram Bug 346404