Eclipse Community Forums: TMF (Xtext) » resolve EClass from base grammar during post processing

Help

Home

Home » Modeling » TMF (Xtext) » resolve EClass from base grammar during post processing

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

resolve EClass from base grammar during post processing [message #1410713]

Thu, 21 August 2014 12:45

Henrik Rentz-Reichert

Messages: 261
Registered: July 2009

Senior Member

Hi,

I have a very special kind of problem.

My grammar derives from another grammar (also written by me).
I have a post processor in place which does some tweaks to the generated model.
This works excellent for various cases with one exception.

If I access a type which is inferred from the base grammar (using the generated BasePackage.eINSTANCE) then I can use it e.g. as a
return type of an operation.
In the debugger I verified that the EClass object is correctly resolved.
But the serialized ecore model then contains proxy URLs for those types.

On the other hand if I use e.g. ECorePackage.eINSTANCE.getEClassifier("EBoolean") then all works fine.

How can I resolve this issue?

Thanks,
Henrik

Report message to a moderator

Re: resolve EClass from base grammar during post processing [message #1410720 is a reply to message #1410713]

Thu, 21 August 2014 13:01

Henrik Rentz-Reichert

Messages: 261
Registered: July 2009

Senior Member

PS: during my further tries I introduced a bug in the post processor which rendered the folder for the generated EMF classes
empty. After I fixed the bug and re-generated the issue below was resolved.
I have no idea though why it works now since I basically didn't change anything :-/

Am 21.08.2014 um 14:45 schrieb Henrik Rentz-Reichert:
> Hi,
>
> I have a very special kind of problem.
>
> My grammar derives from another grammar (also written by me).
> I have a post processor in place which does some tweaks to the generated model.
> This works excellent for various cases with one exception.
>
> If I access a type which is inferred from the base grammar (using the generated BasePackage.eINSTANCE) then I can use it e.g. as a
> return type of an operation.
> In the debugger I verified that the EClass object is correctly resolved.
> But the serialized ecore model then contains proxy URLs for those types.
>
> On the other hand if I use e.g. ECorePackage.eINSTANCE.getEClassifier("EBoolean") then all works fine.
>
> How can I resolve this issue?
>
> Thanks,
> Henrik
>

Report message to a moderator

Re: resolve EClass from base grammar during post processing [message #1411014 is a reply to message #1410720]

Fri, 22 August 2014 07:05

Henrik Rentz-Reichert

Messages: 261
Registered: July 2009

Senior Member

I again got stuck and am not able to resolve this issue.

Any help is appreciated.

Thanks,
Henrik

Am 21.08.2014 um 15:01 schrieb Henrik Rentz-Reichert:
> PS: during my further tries I introduced a bug in the post processor which rendered the folder for the generated EMF classes
> empty. After I fixed the bug and re-generated the issue below was resolved.
> I have no idea though why it works now since I basically didn't change anything :-/
>
> Am 21.08.2014 um 14:45 schrieb Henrik Rentz-Reichert:
>> Hi,
>>
>> I have a very special kind of problem.
>>
>> My grammar derives from another grammar (also written by me).
>> I have a post processor in place which does some tweaks to the generated model.
>> This works excellent for various cases with one exception.
>>
>> If I access a type which is inferred from the base grammar (using the generated BasePackage.eINSTANCE) then I can use it e.g. as a
>> return type of an operation.
>> In the debugger I verified that the EClass object is correctly resolved.
>> But the serialized ecore model then contains proxy URLs for those types.
>>
>> On the other hand if I use e.g. ECorePackage.eINSTANCE.getEClassifier("EBoolean") then all works fine.
>>
>> How can I resolve this issue?
>>
>> Thanks,
>> Henrik
>>

Report message to a moderator

Re: resolve EClass from base grammar during post processing [message #1412631 is a reply to message #1411014]

Tue, 26 August 2014 16:46

Henrik Rentz-Reichert

Messages: 261
Registered: July 2009

Senior Member

here is a line of the ecore model that is produced by Xtext

<eClassifiers xsi:type="ecore:EClass" name="ActorClass" eSuperTypes="#//ActorContainerClass
platform:/resource/org.eclipse.etrice.core.fsm/model/generated/FSM.ecore#//ModelComponent">

after I correct it manually it reads

<eClassifiers xsi:type="ecore:EClass" name="ActorClass" eSuperTypes="#//ActorContainerClass
.../../../../../../org.eclipse.etrice.core.fsm/model/generated/FSM.ecore#//ModelComponent">

So it looks like the platform:/ scheme isn't working

Am 22.08.2014 um 09:05 schrieb Henrik Rentz-Reichert:
> I again got stuck and am not able to resolve this issue.
>
> Any help is appreciated.
>
> Thanks,
> Henrik
>
> Am 21.08.2014 um 15:01 schrieb Henrik Rentz-Reichert:
>> PS: during my further tries I introduced a bug in the post processor which rendered the folder for the generated EMF classes
>> empty. After I fixed the bug and re-generated the issue below was resolved.
>> I have no idea though why it works now since I basically didn't change anything :-/
>>
>> Am 21.08.2014 um 14:45 schrieb Henrik Rentz-Reichert:
>>> Hi,
>>>
>>> I have a very special kind of problem.
>>>
>>> My grammar derives from another grammar (also written by me).
>>> I have a post processor in place which does some tweaks to the generated model.
>>> This works excellent for various cases with one exception.
>>>
>>> If I access a type which is inferred from the base grammar (using the generated BasePackage.eINSTANCE) then I can use it e.g. as a
>>> return type of an operation.
>>> In the debugger I verified that the EClass object is correctly resolved.
>>> But the serialized ecore model then contains proxy URLs for those types.
>>>
>>> On the other hand if I use e.g. ECorePackage.eINSTANCE.getEClassifier("EBoolean") then all works fine.
>>>
>>> How can I resolve this issue?
>>>
>>> Thanks,
>>> Henrik
>>>

Report message to a moderator

Previous Topic:	Slow typing of dsl language, only at the bottom of the document in the dsl editor.
Next Topic:	References across files

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 08:03:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter