[news.eclipse.modeling.mdt.uml2.tools] Re: Problems deleting classes/int

["Michael Golubev" <michael.golubev@xxxxxxxxxxx>]

Hi,

This is caused by the NPE from AssociationEndConvention (complete log is 
attached to the just opened scr 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=166058).

After the class is deleted, an association became incomplete and diagram 
update fails to repaint it.
It is not yet clear for me how to correctly behave in this case, I am not 
sure that deleting association is an expected reaction.

I will take a look at this.

Regards,
Michael


"A. Gómez" <vivaelcieloazul@xxxxxxxxxxxxxx> wrote in message 
news:ekfcto$vtj$1@xxxxxxxxxxxxxxxxxxxx
> Hi all!
>
> I have been working with the UML2 class diagram editor, and I have found a 
> problem in the deletion mechanism of interfaces/classes. If I define two 
> classes, and a an association between them, if I want to delete one of the 
> classes I _must_ delete first the association defined between the clases, 
> and then, the class.
>
> If I try to remove directly the class, the class is not always removed, 
> and the association remains in the *.uml model (but incomplete). Should I 
> post a new bugzilla post for that issue?
>
> And... how can I extend the deletion mechanism to automatically remove the 
> associations (or at least, tell the user to remove first the associations 
> involved manually)? I have tried to modify the method 
> getDestroyElementCommand(...) in 
> org.eclipse.uml2.diagram.clazz.edit.policies.ClassItemSemanticEditPolicy, 
> but I didn't find the way to do it.
>
> Regards,
>
> A. Gómez
>