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
crcrossnamespaceassoc.zargo
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
