Home » Archived » M2M (model-to-model transformation) » [QVTO]Incompatible input type 'modelparam::ResourceEObject', expected 'uml::Model'
| [QVTO]Incompatible input type 'modelparam::ResourceEObject', expected 'uml::Model' [message #79451] |
Wed, 16 April 2008 22:37  |
Eclipse User |
|
|
|
Originally posted by: comouraf-lixo.yahoo.fr
Hi,
I'm getting this error, when I create a new run configuration for my
transformation:
Incompatible input type 'modelparam::ResourceEObject', expected
'uml::Model'
If I provide a plain uml model, everything works fine, but as soon as I
apply a profile (in fact, when I apply a stereotype), the above message is
displayed. Looking at the xml code, we can see that applying a given
stereotype causes the xml root element to change from <uml:model/> to
<xmi:XMI/> in order to accommodate the stereotype applications (which are in
the same level as uml:model).
Any idea on how to solve this problem ?
Thanks,
César
ps: just in case, I use an M6 build.
|
|
|
| Re: [QVTO]Incompatible input type 'modelparam::ResourceEObject', expected 'uml::Model' [message #79466 is a reply to message #79451] |
Thu, 17 April 2008 11:17  |
 Radomil Dvorak
Messages: 249
Registered: July 2009 |
Senior Member |
|
|
Hi César,
Could you please make sure you use signature-less main() entry operation
in your
transformation? I think this is the cause.
Anyway, it looks like you have hit a bug :)
Regards,
/Radek
On Thu, 17 Apr 2008 00:37:28 +0200, kaiserlautern <comouraf-lixo@yahoo.fr>
wrote:
> Hi,
>
> I'm getting this error, when I create a new run configuration for my
> transformation:
>
> Incompatible input type 'modelparam::ResourceEObject', expected
> 'uml::Model'
>
> If I provide a plain uml model, everything works fine, but as soon as I
> apply a profile (in fact, when I apply a stereotype), the above message
> is displayed. Looking at the xml code, we can see that applying a given
> stereotype causes the xml root element to change from <uml:model/> to
> <xmi:XMI/> in order to accommodate the stereotype applications (which
> are in the same level as uml:model).
>
> Any idea on how to solve this problem ?
>
> Thanks,
>
> César
> ps: just in case, I use an M6 build.
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
| Re: [QVTO]Incompatible input type 'modelparam::ResourceEObject', expected 'uml::Model' [message #79506 is a reply to message #79466] |
Thu, 17 April 2008 20:17 |
| Eclipse User |
|
|
|
Originally posted by: comouraf-lixo.yahoo.fr
Hi, Radek,
You're right. Using a main without parameters solves the problem. Thanks.
César
"Radek Dvorak" <radek.dvorak@borland.com> a écrit dans le message de
news:op.t9q5nowwhj1a1g@czprl-rdvorak2.emea.borl.net...
> Hi César,
>
> Could you please make sure you use signature-less main() entry operation
> in your
> transformation? I think this is the cause.
>
> Anyway, it looks like you have hit a bug :)
>
> Regards,
> /Radek
>
>
> On Thu, 17 Apr 2008 00:37:28 +0200, kaiserlautern <comouraf-lixo@yahoo.fr>
> wrote:
>
>> Hi,
>>
>> I'm getting this error, when I create a new run configuration for my
>> transformation:
>>
>> Incompatible input type 'modelparam::ResourceEObject', expected
>> 'uml::Model'
>>
>> If I provide a plain uml model, everything works fine, but as soon as I
>> apply a profile (in fact, when I apply a stereotype), the above message
>> is displayed. Looking at the xml code, we can see that applying a given
>> stereotype causes the xml root element to change from <uml:model/> to
>> <xmi:XMI/> in order to accommodate the stereotype applications (which
>> are in the same level as uml:model).
>>
>> Any idea on how to solve this problem ?
>>
>> Thanks,
>>
>> César
>> ps: just in case, I use an M6 build.
>>
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
Goto Forum:
Current Time: Fri Apr 26 13:01:48 GMT 2024
Powered by FUDForum. Page generated in 0.03132 seconds |
] 
Search
Help
Register
Login
Home
