OK, I've found the root of the problem. It's to do with how ArgoUML determines the permitted namespaces for inheriting classes, i.e. those which are GeneralizableElements, and the rules in this case are (apparently deliberately) very restrictive. See http://argouml.tigris.org/issues/show_bug.cgi?id=3772 for much more background.
As a quick hack to meet my needs, I have simply amended org.argouml.model.mdr.CoreHelperMDRImpl.isValidNamespace(Generalization, Namespace) to always return true, and this change now shows all the namespaces I need. A workaround not requiring code changes is to delete all the generalizations for the relevant class from the model, then set its new namespace, then reinstate the generalizations. When refactoring one regularly moves classes and interfaces around the inheritance hierarchy, often in quite far-reaching ways; if there is a better solution, I'd love to hear it. Sorry if I've missed the point somewhere along the line. Thanks for everyone's input. :) ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2592980 To unsubscribe from this discussion, e-mail: [[email protected]].
