Hi Sebastien,
No I’m reusing
RestoreRelatedLinksCommand
which was implemented on the Activity Diagram. It works fine except for the all Association UML element.
But I think the problem come from the UMLDiagramUpdater implementation class. Because the problem appears on the UseCase
Diagram to (I’m implementing the restore related element on this diagram to).
I have found a work around for this the bug(https://bugs.eclipse.org/bugs/show_bug.cgi?id=359684)
which work now. But I would like have your feedback on this.
Have you already try the GMF mechanism? If yes have you noticed a similar problem?
Regards
Arthur Daussy.
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : lundi 3 octobre 2011 13:55
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] [UMLDiagramUpadter] Worng implementation of generated code
Hi Arthur,
About this function, there is a possible behavior in GMF (not currently implemented in Papyrus) to do it, by double-click
on the link accelerator of element. Do you implement that?
Thanks,
Sébastien.
------------------------------------------------------------------------------------------------------------------------------------------------
Sébasten Gérard
CEA LIST, Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),
Point Courrier 94, Gif-sur-Yvette, F-91191 France
www.eclipse.org/papyrus
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de DAUSSY Arthur
Envoyé : lundi 3 octobre 2011 12:31
À : Papyrus Project list
Objet : [mdt-papyrus.dev] [UMLDiagramUpadter] Worng implementation of generated code
Hello,
I’m currently working on the “Restore Related Elements” action on the Class diagram. I’m writing on this list in order to put in light an implementation
problem on the UMLDiagramUpdater class.
Indeed, this class is used to get the incoming and outgoing link of a node. However this class has a strange behavior when dealing with association
(UML Class diagram).
Example:
In a model containing:
è
<Class>Class0
è
<Class>Class2
è
<Class>Class1
è
<Association>Class0_Class1.
è
<Association>Class0_Class2
org.eclipse.papyrus.diagram.clazz.part.UMLDiagramUpdater.getIncomingTypeModelFacetLinks_Association_4001(Type, Map<EObject, Collection<Setting>>)
return the following
collection of UMLLinkDescriptor : [ Desc1{src:Class0,target:Class0} , Desc2{rc:Class0,target:Class0}]
Whereas
org.eclipse.papyrus.diagram.clazz.part.UMLDiagramUpdater.getOutgoingTypeModelFacetLinks_Association_4001(Type)
return
the following collection of UMLLinkDescriptor : [ Desc1{src:Class0,target:Class1 , Desc2{src:Cass0,target:Class2}]
This is a critical bug for us so a quick fix has been committed on the branch 0.8.X with the following bug:
359684: [Class Diagram] Restore Related Elements with association add an extra association
https://bugs.eclipse.org/bugs/show_bug.cgi?id=359684
So I would like to discuss on the bug the suggested solution in order to correctly implement a solution which can be backported on the trunk.
Regards,
Arthur Daussy

|
Arthur Daussy
Atos Origin Intégration
6 impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3
Telephone : +33 (0) 5 34 36 32 90
www.atos.net
|
Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret
professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de
ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet,
the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting
from any virus transmitted.