29 Apr 2009 16:49
Re: Re: best practice to build profile for argouml 0.28
Vincent Fretin <vincent.fretin <at> gmail.com>
2009-04-29 14:49:28 GMT
2009-04-29 14:49:28 GMT
On Wed, Apr 29, 2009 at 4:35 PM, Tom Morris <tfmorris <at> gmail.com> wrote:
For now all tagged-values can be used anywhere. We don't use the "tag definitions are associated with a stereotype" functionality. We should indeed.
A year or two ago, I patched the ArchGenXML profile generator to
prepare it for our new profiles by providing stable xmi.id values, but
the patch also included some other functional improvements as well. I
think, but am not sure, that I provided the patch to either the Plone
bug system or as an attachment/comment on one of the doc pages. Do
you have that patch? If not, I can see if I can resurrect it.
Now the archgenxml_profile.xmi use stable xmi.id.
I saw nowhere your patch. You already said that when I implemented stable xmi.id with the uuid module, but it seems your patch was never commited....
I saw nowhere your patch. You already said that when I implemented stable xmi.id with the uuid module, but it seems your patch was never commited....
It sounds to me that both of these constraints can be handled by the
fundamental constraints of the Stereotype/TaggedValue system.
Stereotypes have base classes which constrain what elements they can
be applied to. TagDefinitions are owned by Stereotypes and can only
be applied to elements which have those Stereotypes applied. Are you
using this functionality or are you falling back to UML 1.3
compatibility mode where anything can be applied to anything?
Tom
For now all tagged-values can be used anywhere. We don't use the "tag definitions are associated with a stereotype" functionality. We should indeed.

--
Vincent Fretin

RSS Feed