|Unexpected interaction between UML Association#ownedEnds and DeleteCommand - AssocTest.java (1/1) [message #628334]
||Tue, 23 March 2010 15:15
| Volker Stolz
Registered: July 2009
Dear all, the attach small JUnit4 test for the Eclipse Modeling Tools
20100218-1602 triggers the 1 1/2 assertions at the bottom of the file.
The problem is that the DeleteCommand removes the association from the
model, but since the association has still the type 'a1' pointing "into"
the model, a1.getAssociations() still includes the just deleted
Am I missing some special EMF initialisation that prevents this change
from being tracked? Is this expected behaviour? If yes, what is the
suggested way of "traversing" an association (and similar cases) and
removing/unsetting the corresponding values?
For good measure, even EcoreUtil.remove(assoc) has the same behaviour.
The test case exercises both a "plain" UML/EMF code-path using setters,
and an alternative using EMF commands.
United Nations University -
Powered by FUDForum
. Page generated in 0.02309 seconds