> It seems to make sense to define and maintain these entities in one > place and import them into each model in much the same way that the > basic AndroMDA entities are incorporated into the model at > the start of a AndroMDA project. > > Is there some way to do this, using ArgoUML, so that changes > to the core > entities can be easily replicated to all of the portlet > models without > having to go to each model and manually change each class in the core > that has changed.
There isn't a good way to do this right now. Our current profile mechanism uses copy-on-reference semantics, so even if a profile were powerful enough to meet your needs, you'd be left with stale versions of the elements (stereotypes, etc) which had been copied into your project that wouldn't reflect any updates to the profile. This enhancement request http://argouml.tigris.org/issues/show_bug.cgi?id=3497 deals with this issue, so you can add your votes there. Some of the underlying framework needed to implement our improved profile support (a Google Summer of Code project) will also benefit what you want to do, so you should see improvements by the end of the summer. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
