1
Automation Interface, Add-Ins and Tools / Re: UML Patterns
« on: June 05, 2008, 04:05:56 pm »
L.S.,
I have gone a bit further and added shortcuts (simple links) of the super classes to the classdiagram. When exporting this pattern, the super classes are set to merge; all the other classes are set to be created. After reimporting this as a pattern, I have to merge or link the super classes back to their actual location in the eap file. And after dropping the classes on a new classdiagram, I remove the shortcuts to the super classes and I have got what I want.
I can understand that a UML pattern ignores packages and therefore the actual location of classes in the eap file, but in my case classes always inherit functionality from the same particular super classes, that are always in the same location in the eap file.
So, is there a way to do the import with an automated merge, since the location of the super classes in the eap is already known in the xml pattern file, designated by the namespace.
TIA and regards,
Will
I have gone a bit further and added shortcuts (simple links) of the super classes to the classdiagram. When exporting this pattern, the super classes are set to merge; all the other classes are set to be created. After reimporting this as a pattern, I have to merge or link the super classes back to their actual location in the eap file. And after dropping the classes on a new classdiagram, I remove the shortcuts to the super classes and I have got what I want.
I can understand that a UML pattern ignores packages and therefore the actual location of classes in the eap file, but in my case classes always inherit functionality from the same particular super classes, that are always in the same location in the eap file.
So, is there a way to do the import with an automated merge, since the location of the super classes in the eap is already known in the xml pattern file, designated by the namespace.
TIA and regards,
Will