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.
More comments below... On Mon, Apr 27, 2009 at 4:29 AM, Jens Klein <[email protected]> wrote: > Am Sun, 26 Apr 2009 11:18:56 +0200 schrieb Marcos Aurélio: >>> >>> Is it possible to express this kind of constraint in XMI and within >>> ArgoUML? A tiny example or a simple "No way" would help me a lot. >>> Searching the web brought up tons of crap results, but no good document >>> explaining XMI and UML-Profiles in depth. >>> >>> >> Hi, I think you can represent this adding an OCL annotation to your profile > > the current profile xmi file is located here: > https://svn.plone.org/svn/archetypes/ArchGenXML/trunk/umltools/argouml > > Example 1: > > I'd like to tell the tag definition to be valid only on "Class" elements. > > Example 2 > --------- > the following shoudl be allowed only on classes with the stereotype > <<tool>> > > the stereotype <<tool>> should be allowed only on classes. > > Id really appreciate examples for both. As you see in the file we have > lots of tagged values and selecting them from this very long drop-down in > argouml is no fun. > > Different topic, but it would also help if the dropdown helps selecting > the value by jumping to the entry by pressing its first letter. This is > not so important if we can reduce the list to relevant entries only using > the OCL-approach you mentioned. 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 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=1980738 To unsubscribe from this discussion, e-mail: [[email protected]].
