Eclipse Community Forums: UML2

Help

Home

Home » Modeling » UML2 » Redefinition

Show: Today's Messages :: Show Polls :: Message Navigator

Redefinition [message #478148]

Mon, 02 February 2009 15:04

Alexandre Torres

Messages: 139
Registered: July 2009

Senior Member

Hi.
I'm creating a profile where stereotype B extends stereotype A. Stereotype
A extends the uml::Class, by the extension_A/base_Class relation.
I created a relation btw B and Class called extension_B/base_Class. I want
it to redefine extension_A.
When I execute OCL constraints in my model, extension_B is not recognized.
The good news is that base_Class works for both A and B, and I can still
use the extension_A on both stereotypes.
Until now I just set the Redefined property of my extension_B to point
extension_A, but can't figure out what to put on the member end
association.
If I create a new property base_Class on extension_B, using the redefine
property pointing to extension_A's base_Class, I get warnings from the
"define" menu about duplication and "should be annotated as redefinition".
There are so many options here that I'm a bit lost. If someone has a
example model that I could download and learn what I'm doing wrong, it
would really help.
Is there some emf annotation I need to add to the model?

Thanks

Report message to a moderator

Re: Redefinition [message #478176 is a reply to message #478148]

Fri, 06 February 2009 20:59

james bruck

Messages: 1724
Registered: July 2009

Senior Member

Hi Alexandre,

I've cc'd this on the OCL newsgroup in case there is some more input from
there.
Would it be possible to attach the profile you are trying to build. There
may be some confusion between "Extend" and "Generalization" relationships.
Also I'm a bit confused as to why you want to redefine the extension_A.
It may be easier to respond if I had the bigger picture of what you are
trying to achieve.

I agree that all the genmodel options are somewhat confusing and this is an
area that is screaming for some documentation.
I'll try to put something together.

Cheers,
- James.

"Alexandre Torres" <alexandre.torres@gmail.com> wrote in message
news:a281809702b23dae9dd6fa652f130de2$1@www.eclipse.org...
> Hi.
> I'm creating a profile where stereotype B extends stereotype A. Stereotype
> A extends the uml::Class, by the extension_A/base_Class relation.
> I created a relation btw B and Class called extension_B/base_Class. I want
> it to redefine extension_A.
> When I execute OCL constraints in my model, extension_B is not recognized.
> The good news is that base_Class works for both A and B, and I can still
> use the extension_A on both stereotypes.
> Until now I just set the Redefined property of my extension_B to point
> extension_A, but can't figure out what to put on the member end
> association.
> If I create a new property base_Class on extension_B, using the redefine
> property pointing to extension_A's base_Class, I get warnings from the
> "define" menu about duplication and "should be annotated as redefinition".
> There are so many options here that I'm a bit lost. If someone has a
> example model that I could download and learn what I'm doing wrong, it
> would really help.
> Is there some emf annotation I need to add to the model?
>
>
> Thanks
>
>

Report message to a moderator

Re: Redefinition [message #478179 is a reply to message #478176]

Mon, 09 February 2009 16:09

Eclipse User

Originally posted by: cdamus.zeligsoft.com

Hi, Alexandre,

Are you using the OCL constraints facility as generated by UML2? If so,
then this isn't working because UML2 generates OCL constraint code using
the Ecore metamodel binding, not the UML metamodel binding. Thus, the
OCL constraint parsing and evaluation is done in terms of Ecore, which
does not have the notion of non-navigable property navigation (such as
in the case of extension_B or even extension_A, for that matter).

With the UML metamodel binding, OCL will recognize the extension_B
property, but I'm not sure that it will treat it as a redefinition of
extension_A in all respects.

HTH,

Christian

James Bruck wrote:
> Hi Alexandre,
>
> I've cc'd this on the OCL newsgroup in case there is some more input from
> there.
> Would it be possible to attach the profile you are trying to build. There
> may be some confusion between "Extend" and "Generalization" relationships.
> Also I'm a bit confused as to why you want to redefine the extension_A.
> It may be easier to respond if I had the bigger picture of what you are
> trying to achieve.
>
> I agree that all the genmodel options are somewhat confusing and this is an
> area that is screaming for some documentation.
> I'll try to put something together.
>
> Cheers,
> - James.
>
> "Alexandre Torres" <alexandre.torres@gmail.com> wrote in message
> news:a281809702b23dae9dd6fa652f130de2$1@www.eclipse.org...
>> Hi.
>> I'm creating a profile where stereotype B extends stereotype A. Stereotype
>> A extends the uml::Class, by the extension_A/base_Class relation.
>> I created a relation btw B and Class called extension_B/base_Class. I want
>> it to redefine extension_A.
>> When I execute OCL constraints in my model, extension_B is not recognized.
>> The good news is that base_Class works for both A and B, and I can still
>> use the extension_A on both stereotypes.
>> Until now I just set the Redefined property of my extension_B to point
>> extension_A, but can't figure out what to put on the member end
>> association.
>> If I create a new property base_Class on extension_B, using the redefine
>> property pointing to extension_A's base_Class, I get warnings from the
>> "define" menu about duplication and "should be annotated as redefinition".
>> There are so many options here that I'm a bit lost. If someone has a
>> example model that I could download and learn what I'm doing wrong, it
>> would really help.
>> Is there some emf annotation I need to add to the model?
>>
>>
>> Thanks
>>
>>
>
>

Report message to a moderator