|
|
|
Re: Link Constraint with oclIsKindOf [message #125410 is a reply to message #125057] |
Thu, 10 May 2007 12:12 |
Radomil Dvorak Messages: 249 Registered: July 2009 |
Senior Member |
|
|
Hi Mathias,
Use both type names as qualified, the way Alex has suggested.
As you use two metamodels, it is unclear which package was taken
as the default one for resolving un-qualified names.
If you have tried so already, could you please post a simple test models
that we could reproduce this?
Regards,
/Radek
On Thu, 10 May 2007 09:39:41 +0200, Mathias Freier
<mathias.freier@gentleware.com> wrote:
> Hello Alex,
>
> I tried (in several variations: ::, : , fqn ...), but it does not work.
>
> Mathias
>
> Alex Shatalin schrieb:
>> Hello Mathias,
>> Try using entity::EntityConstants as a parameter of oclIsKindOf.
>> -----------------
>> Alex Shatalin
>>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
Re: Link Constraint with oclIsKindOf [message #129205 is a reply to message #125410] |
Thu, 24 May 2007 10:33 |
Eclipse User |
|
|
|
Originally posted by: bhatia1984.yahoo.com
hiiiii
I am also facing the same prob
I hv two metamodels Tde & UseCase
All the elements in UseCase extends from DiagramElement which i hv defined
in Tde & also the diagram of usecase extends from class which i hv define
in Tde.
By the way UseCase is usecase editor & Tde is statemachine editor.
now when i define
self.ocliskindof(Actor) in usecase it gives error.
but when i define
self.ocliskindof(StartState) in Tde it works fine.
i tried to define
self.ocliskindof(Actor::DiagramElement) but still it gives error.
what i want is that i dnt want any incoming transition on actor
Thanks
Varun Bhatia
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04432 seconds