| Operational QVT Interpreter [message #946881] |
Tue, 16 October 2012 15:43  |
Eclipse User |
|
|
|
Hello,
when I define a debug/launch config for the Operation QVT Interpreter,
which meta model registry does it use? When I select my .qvto script, it
correctly lists input and output models, but whatever input file I
specify, it's always rejected.
Previously I loaded all relevant models into the global EMF registry and
attached a file suffix to it. How is this supposed to work with the
per-project metamodel map?
Thanks
Marius
|
|
|
|
| Re: Operational QVT Interpreter [message #947717 is a reply to message #946906] |
Wed, 17 October 2012 11:01  |
| Eclipse User |
|
|
|
Hello Ed,
actually my question was this: how does the Operational QVT Interpreter
determine the i/o models - does it use the metamodel map of the project
hosting the qvto file?
Thanks
Marius
On 16.10.2012 18:12, Ed Willink wrote:
> Hi
>
> As a general rule only Eclipse plugins (and standalone code emulating
> Eclipse plugins) should modify the global EMF registries.
>
> If the input file is rejected, I suspect that in some sense it is
> incompatible with what you have specified. But you provide no real
> details to go on.
>
> I'm afraid that I will not be able to give you any further help without
> a zipped project including a launch configuration that can just be
> installed and run to demonstrate your problem.
>
> Regards
>
> Ed Willink
>
> On 16/10/2012 16:43, Marius Gröger wrote:
>> Hello,
>>
>> when I define a debug/launch config for the Operation QVT Interpreter,
>> which meta model registry does it use? When I select my .qvto script, it
>> correctly lists input and output models, but whatever input file I
>> specify, it's always rejected.
>>
>> Previously I loaded all relevant models into the global EMF registry and
>> attached a file suffix to it. How is this supposed to work with the
>> per-project metamodel map?
>>
>> Thanks
>> Marius
>
|
|
|
| Re: Operational QVT Interpreter [message #947751 is a reply to message #947717] |
Wed, 17 October 2012 11:49 |
 Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi
I don't know. It works for me which is why I need to see an example of
what doesn;t work to be able to comment further.
Regards
Ed Willink
On 17/10/2012 12:01, Marius Gröger wrote:
> Hello Ed,
>
> actually my question was this: how does the Operational QVT Interpreter
> determine the i/o models - does it use the metamodel map of the project
> hosting the qvto file?
>
> Thanks
> Marius
>
> On 16.10.2012 18:12, Ed Willink wrote:
>> Hi
>>
>> As a general rule only Eclipse plugins (and standalone code emulating
>> Eclipse plugins) should modify the global EMF registries.
>>
>> If the input file is rejected, I suspect that in some sense it is
>> incompatible with what you have specified. But you provide no real
>> details to go on.
>>
>> I'm afraid that I will not be able to give you any further help without
>> a zipped project including a launch configuration that can just be
>> installed and run to demonstrate your problem.
>>
>> Regards
>>
>> Ed Willink
>>
>> On 16/10/2012 16:43, Marius Gröger wrote:
>>> Hello,
>>>
>>> when I define a debug/launch config for the Operation QVT Interpreter,
>>> which meta model registry does it use? When I select my .qvto script, it
>>> correctly lists input and output models, but whatever input file I
>>> specify, it's always rejected.
>>>
>>> Previously I loaded all relevant models into the global EMF registry and
>>> attached a file suffix to it. How is this supposed to work with the
>>> per-project metamodel map?
>>>
>>> Thanks
>>> Marius
|
|
|
Powered by
FUDForum. Page generated in 0.03162 seconds
] 
Search
Help
Register
Login
Home
