Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Applying mutliple same stereotype
Applying mutliple same stereotype [message #1008665] Wed, 13 February 2013 09:15 Go to next message
E. TOSI is currently offline E. TOSI
Messages: 10
Registered: July 2012
Junior Member
Hi,

I use Stereotype on Properties to generate C# Attributes

When a stereotype is already applied on Property we cannot add the same one multiple times ?

Why this a limitation ?

Thanks in advance,

-----
Papyrus 0.9.0
Re: Applying mutliple same stereotype [message #1008674 is a reply to message #1008665] Wed, 13 February 2013 09:28 Go to previous messageGo to next message
Christian W. Damus is currently offline Christian W. Damus
Messages: 779
Registered: July 2009
Senior Member
Hi,

That is the how the UML Specification defines that stereotypes work:
the upper bound of the ExtensionEnd of a metaclass Extension may not be
more than 1. A stereotype, by definition, can only be applied once.

If your stereotype needs to carry multiple values of its properties,
then its properties need to have multiplicity in themselves.

HTH,

Christian


On 2013-02-13 14:15:18 +0000, E. TOSI said:

> Hi,
>
> I use Stereotype on Properties to generate C# Attributes
>
> When a stereotype is already applied on Property we cannot add the same
> one multiple times ?
>
> Why this a limitation ?
>
> Thanks in advance,
>
> -----
> Papyrus 0.9.0
Re: Applying mutliple same stereotype [message #1008972 is a reply to message #1008674] Thu, 14 February 2013 03:26 Go to previous messageGo to next message
E. TOSI is currently offline E. TOSI
Messages: 10
Registered: July 2012
Junior Member
Hi Christian,

Thanks for your response.

I will modify my Stereotypes to accept multiples values and satisfy this UML specification.

Regards,
Eric
Re: Applying mutliple same stereotype [message #1011338 is a reply to message #1008972] Tue, 19 February 2013 05:52 Go to previous message
Eclipse User
A stereotype in UML 2 is not a simple name-value pair as it was in UML 1.x.
Applying a stereotype to a metaclass means changing the metaclass to the
stereptype, i.e., a Class with <<requirement>> is considered to be a
requirement instead of class. So, adding the same stereotype would not make
sense at all.

HTH,

Marc-Florian

"E. TOSI" schrieb im Newsbeitrag news:kfi73a$emd$1@xxxxxxxxe.org...

Hi Christian,

Thanks for your response.

I will modify my Stereotypes to accept multiples values and satisfy this UML
specification.

Regards,
Eric
Previous Topic:Modeling Papyrus Marte
Next Topic:how to create a popup menu in eclipse using commands and handlers
Goto Forum:
  


Current Time: Mon Sep 01 07:40:15 EDT 2014

Powered by FUDForum. Page generated in 0.02749 seconds