[news.eclipse.modeling.mdt.uml2] Re: Creating Stereotype extending Assoc

["Christian W. Damus" <cdamus@xxxxxxx>]

Hi, Gilbert,

If you need to constrain a stereotype to be applied only to association ends, then you can do that with another OCL constraint:

  context MyProfile::Event
  inv is_association_end: base_Property.association.oclIsUndefined()

HTH,

Christian

On Thu, 2009-06-04 at 11:15 +0200, Gilbert Mirenque wrote:
> Hi Vlad,
>
> > My article is available at:
> > http://www.forum-omondo.com/documentation_eclipseuml_2008/Association_ends_stereotypes.html
>
>
> thanks for your article. Nice possibility to apply stereotypes to
> association ends. But I think that it is only possible in this way with
> the Omondo Modeler because other UML-Tools, such as TOPCASED, don't
> display the specified association-names as attributes in the class (see
> the attached screenshots). That means one has first to open the
> generated  uml-file, select the association-end-property, and apply the
> stereotype via the uml2tools from eclipse. Well, the stereotype is
> applied but it isn't visible in the diagram. Another issue is that you
> could apply the associationEnd-stereotype to any property of a class -
> not only to associationEnds.
> But a big thank you for your article. I could solve my problem in
> another way. I found out that I can model my concerns better with a
> StateMachine and not with a ClassDiagram. There I extended the
> Pseudostate metaclass.
>
> best regards,
> Gilbert