Bug 448398 - Sometimes a model element loses its LazyCrossReferencer adapter after changing the container
Summary: Sometimes a model element loses its LazyCrossReferencer adapter after changin...
Status: CLOSED WONTFIX
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 2.0.1   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-10-22 11:54 EDT by Mickael LANOE CLA
Modified: 2014-12-12 10:16 EST (History)
2 users (show)

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 Mickael LANOE CLA 2014-10-22 11:54:05 EDT 
In a particular context, some model elements lost there LazyCrossReferencer after changing the container. 

The LazyCrossReferencer adapter is removed from a model element on the REMOVE/UNSET notification and added on the ADD/SET notification.

In this case, when the container of a model element is changed, the ADD/SET notification is called before the REMOVE/UNSET notification. So the LazyCrossReferencer adapter no longer exists in the adapter list of the model element.
Comment 2 Laurent Redor CLA 2014-10-23 12:27:25 EDT 
The issue is reopened, it causes some unexpected regression on JUnit tests and needs further investigation.
Comment 3 Mickael LANOE CLA 2014-11-05 07:47:27 EST 
This issue was fixed in other way thank to  https://bugs.eclipse.org/bugs/show_bug.cgi?id=449045
Comment 4 Pierre-Charles David CLA 2014-12-12 10:16:54 EST 
Available in Sirius 2.0.1.