What I forgot to mention: ArgoUML triggers as well for the "don't
trigger" cases, as it does not evaulate the import relations.
Markus
Markus Klink wrote:
This is for
http://argouml-stats.tigris.org/documentation/manual-0.22/ch15s11.html#critics.CrCrossNamespaceAssoc
The description there and in the corresponding class
CrCrossNamespaceAssoc is fairly wrong.
The reason why all association ends must be in the same namespace is
because UML requires the namespaces to be imported into each other. I
created a diagram to illustrate this. ArgoUML would be capable to
implement this, but we never really looked at it.
I would be grateful if the text could be removed from the manual. I
also attached a zargo file with the image for reference.
Thanks,
Markus
------------------------------------------------------------------------
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
