| Summary: | org.eclipse.papyrus.diagram.clazz.edit.parts.AssociationEditPart cannot be cast to org.eclipse.gmf.runtime.diagram.ui.editparts.GraphicalEditPart | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | yirco <netswengineer> |
| Component: | Diagram | Assignee: | Camille Letavernier <cletavernier> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Patrick.Tessier |
| Version: | 0.8.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
yirco
Fixed in r8444. The fix will only prevent diagram corruption, but there's a deeper problem here. When trying to create an Association Class (And maybe also an Association) between an Association and a Class, there are a few exceptions. The command will be reverted, and the diagram won't be corrupted. However, when you retarget an existing association/associationClass' end to an Association, the command will be executed ; and you won't be able to open your diagram afterwards. We should determine whether this should be allowed or not. It seems valid according to the UML specification, as an Association is actually a Classifier ; but it still seems strange. Anyway, the diagram should not be corrupted anymore, now. > However, when you retarget an existing association/associationClass' end to an Association, the command will be executed ; and you won't be able to open your diagram afterwards. We should determine whether this should be allowed or not. It seems valid according to the UML specification, as an Association is actually a Classifier ; but it still seems strange.
This now works as expected in the latest version of Papyrus. I close this task.
|