Community
Participate
Working Groups
Actually, the org.eclipse.gmf.runtime.emf.type.core.requests.MoveRequest contains information about moved element, target container and optionally the target feature to be used for moved element. In context of UML2Tools, processing of some moves requires information about actual semantic element that is diagram parent of the moved element. It is basically all the cases when diagram relationship between element and container is not a semantic containment. E.g, at UseCases diagram, component visually owns the usecases that have it as their subject (Classifier#getUseCases / UseCase#getSubjects). Its not a containment reference, and it may result in the case when single semantic UseCase is visually owned by two different Components. While moving this UseCase from one of its Components, we want to remove it from the actualContainer#getUseCases() list, but not from the otherComponentThatHasTheSameUseCaseButWasNotAffectedByTheMove#getUseCases(). Right now we can't do it correctly because MoveRequest does not provide any information about container for this particular move.
Created attachment 104867 [details] Demonstrates the changes we made in the U2T to workaround the problem
[GMF Restructure] Bug 319140 : product GMF and component Runtime Diagram was the original product and component for this bug