While looking at issue 5301 a theory occured to me and it proved true.

Try drawing a generalization so that a profile class extends a user
class (with diagram toolbar or with toolbelt).

We get an exception dumped to the console.

If I then do View->XmlDump I can see that there has been a
generalization created and it's outside the model.

There have been several reports of this sort of problem in activity
graphs. We need to look at them to see how we might be able to
generate exceptions by dropping transition ends in the wrong place.

I think we should start to move any of the public model interface
factory methods so that they take a namespace or a container as an
argument and allocate immediately after construction. This should
minimise the scope for an exception to occur and leave a model element
out of the model and also make it easier for us to catch an exception
within that method and rollback to remvoe the element if we fail to
place it correctly.

Bob.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to