On Sat, May 30, 2009 at 7:26 AM, Andreas Rueckert <[email protected]> wrote:
> At this point, I don't think the XMI is the problem. It's the Argo code to > create diagrams, that > requires the namespace: > > DiagramFactory.getInstance().createDiagram( > DiagramFactory.DiagramType.Activity, > > Model.getFacade().getNamespace(graph), > > graph); > > And since graph is now a UML2 activity (without any assigned namespace), this > call fails. > > Maybe we could create a baviored classifier to store the namespace in, as > Thomas suggested, but > I doubt that's it's a 1:1 replacement, since the whole navigation is > different then. The main reason that diagrams have a namespace associated with them is to provide default owner/namespace for newly created elements which are created "on" the diagram. Users generally expect them to have the same context as all the other stuff in the same view. I'd argue that all UML Elements should be owned by something in the user's Model. A Model is namespace, as is a Package, and many many other kinds of elements. It shouldn't be that hard to find a workable default home for an Element. Things which aren't in the containment hierarchy won't show up in several of the explorer views and have a good chance of not getting serialized to the XMI file when you say "serialize Model <foo> and all its contents." Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2357144 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
