Hello, Why Add/RemoveAssociationEvent uses 4 events: 2 Add/RemoveAssociationEvents and 2 AttributeChangeEvents.
I tested both the MDR implementation and the eUML implementation with only 1 event, the container where the object will be added is notified about the associaion of it's child with him. I notify ArgoUML of this with a AddAssociationEvent(container, ..., child, ...). I did not notice any difference in ArgoUM's behavior: the panels are showing the same info, the diagrams also, code generation, etc. Anyway, I've implemented all of the 4 events for Add/RemoveAssociationEvents in eUML, but I'm just curious why this is this way. Bogdan, --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
