Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332194 - Dangling cross-references remain after deletion.
Summary: Dangling cross-references remain after deletion.
Status: NEW
Alias: None
Product: MMT.ATL
Classification: Modeling
Component: emfvm (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: mmt-atl.toolkit-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-09 03:48 EST by Salvador Martínez CLA
Modified: 2010-12-09 03:48 EST (History)
0 users

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 Salvador Martínez CLA 2010-12-09 03:48:49 EST 
the method "public void delete(AbstractStackFrame frame, Object modelElement)" in org.eclipse.m2m.atl.engine.emfvm.adapter.EMFModelAdapter does not remove cross-references that may point to the removed element.
Consequently a "object [...] is not contained in a resource" error will be shown on the console when serializing to XMI.

Although, the XMI file will be correct because EMF simply does not serialize the dangling edge, this is problematic in the case when the in-memory model is reused without serialization-deserialization.