Hi,
Yes, these are classic symptoms of missed refactorings. Usually the only recovery is by editing the resource with a generic editor that knows/assumes as little as possible about the semantics of the model. Often this is the text editor (ugh) but sometimes the Sample Reflective Ecore Model Editor can do the job more conveniently (maintaining XML/XMI integrity etc.). It may complain about unresolved proxies and other problems, throwing up the error page, but the tree editor page can still be used to snip out broken/obsolete content, replace broken references, etc.
On 26 July, 2016 at 04:15:39, SCHNEKENBURGER Remi 211865 (remi.schnekenburger@xxxxxx) wrote:
Hi Ernesto,
Indeed this is more a Papyrus-related question than a Papyrus-RT one. The references in the notation seem to come from issues coming from renaming or a copy/paste
action.
From the renaming aspects, Quentin on our side is working back on a refactoring integration proposed some time ago by Gabriel Pascual [1]. This should fix the
issues while renaming resources, which is not handled by EMF. It would be however very nice to understand how we could came in such a situation.
To fix these issues, there is currently no tool AFAIK. Perhaps Christian know better some better solution than a search and replace, there may be some ‘look for
dead references’ ability in Papyrus or emf/uml2 projects.
To fix the notation, I would currently try a seach and replace, or a simple delete. In your example, the first diagram with wrong references to “model.uml” is
a diagram with no element, it can be deleted without losing information.
Regards,
Rémi
[1] https://git.eclipse.org/r/57720
-------------------------------------------------------
Rémi SCHNEKENBURGER
+33 (0)1 69 08 48 48
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
 www.eclipse.org/papyrus
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Ernesto Posse
Envoyé : vendredi 22 juillet 2016 17:18
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [papyrus-rt-dev] Corrupted notation files
Hi team.
I have a couple of questions, although they may be more of a Papyrus issue rather than an -RT issue, but I thought about checking here first.
I have a model in the repo called PingPong-data, under models/tests. When dealing with some codegen issued I saw that for some reason, whenever I loaded this model, it also added a "model.uml" and "PingPong.uml" to the resource set, even
if there where no such models in the workspace. Furthermore, when I tried to use the new model comparison capabilities, it failed with errors referring to those missing references. Now, the PingPong-data.uml model does not have any references to those other
models, but it turns out that for some reason the .notation file has these references.
So I have a couple questions.
1) how can such references exist in the .notation? I'm guessing that maybe some renaming occurred at some point,
2) how can the user avoid such incorrect references?
3) is there a way to fix the .notation without having to recreate the model?
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
