Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329353 - [Profile Diagram] Drop Dependency with an Association as client or supplier throws Exception
Summary: [Profile Diagram] Drop Dependency with an Association as client or supplier t...
Status: RESOLVED INVALID
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Patrick Tessier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 329346
  Show dependency tree
 
Reported: 2010-11-03 10:27 EDT by Vincent Lorenzo CLA
Modified: 2011-05-19 05:34 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 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 CLA 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 CLA 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 CLA 2010-11-04 04:29:55 EDT 
Done in r3110.
Comment 4 Patrick Tessier CLA 2011-05-19 05:34:54 EDT 
dependency and mutli-dependency must not be designed in the profile diagram Bug 346404