[oclinecore] Changing NsURI leaves stale content

[eclipse-ocl-bot]

| --- | --- | | Bugzilla Link | 467998 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | May 22, 2015 07:24 EDT | | Modified | May 23, 2015 06:38 EDT | | Reporter | Ed Willink |

Description

A trimmed repro of the OCLinEcore turorial. Given an (OCLin)Ecore document. e.g.

package example : ex = 'http://www.example.org/examples/example.ecore'\ {\ class Example\ {\ attribute name : String[?];\ property children : Example[*] { ordered composes };\ }\ }

Change the NsURI to e.g. http://www.example.org/examples/example1.ecore

The stale reference results in:

Multiple markers at this line

• The feature 'pivot::Property::opposite' of 'example::Example::children' contains a dangling reference 'Example'
• Unresolved Type '::Example'

[eclipse-ocl-bot]

By Ed Willink on May 23, 2015 06:37

JUnit repro shows up a different problem: testEdit_Past_NsURIcauses problems becuase the NsURI edit is not treated as a CompletePackage delete/add. Easy fix: copy the setName functionality.

commit 0c8150bf71ab742ea0ae61406653d11951a9dba3

The interactive problem is caused by validation of the Orphanage before GC has freed up the weak references to orphans. Could wake up the GC, but easier and faster to just bypass validation for the Orphanage.

commit 438fe2d2724291b4098609b6864c9fddfcc081e4

Pushed to master for RC2.