Eclipse Community Forums: TMF (Xtext) » ScopeProvider with imported Xcore

Help

Home

Home » Modeling » TMF (Xtext) » ScopeProvider with imported Xcore

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

ScopeProvider with imported Xcore [message #1385584]

Mon, 09 June 2014 17:56

Florian König

Messages: 30
Registered: June 2014

Member

Hi,

I need some help with a Xtext ScopeProvider for my DSL.
My goal is to create a cross reference to a Xcore file.

My example DSL looks like this:

grammar org.xtext.example.mydsl.MyDsl with org.eclipse.xtext.common.Terminals
generate myDsl "http ://www.xtext.org/example/mydsl/MyDsl"

import "http ://www.eclipse.org/emf/2011/Xcore" as xcore

Model:
	imports+=Import+
	selection=Selection;

Import:
	'import' importURI=STRING;

Selection:
	'selection' name=ID '{'
		selected=Select
	'}';

Select:
	'select' class=[xcore::XClass] name=ID;

With a simple Xcore file like:

package org.test

class RailCab {
	op void endOfTrackSectionReached()
}

I want do do something like this:

import "test.xcore"

selection test
{
	select RailCab rc
}

But I don't know how to get into the Xcore file in my ScopeProvider.
Can anyone help me with that?

Thanks for any suggestions,
Florian

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385613 is a reply to message #1385584]

Tue, 10 June 2014 04:09

Christian Dietrich

Messages: 14664
Registered: July 2009

Senior Member

Hmm afaik xcore only indexes EClasses. (Check this with the open
model element dialog) so you may change the grammar to

Xxx=[score::EClass] or change xcores resource service provider (
debug xvoreresourcedescriptionstrategy,)

Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385614 is a reply to message #1385613]

Tue, 10 June 2014 04:10

Christian Dietrich

Messages: 14664
Registered: July 2009

Senior Member

Sorry should read [ecore:: EClass|FQN]

Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385627 is a reply to message #1385613]

Tue, 10 June 2014 07:23

Ed Merks

Messages: 33133
Registered: July 2009

Senior Member

Christian,

The things in the GenModel are also indexed, so generally one should try
to reference the Gen* things (and then it will be possible to reference
a model regardless of whether it's in *.xcore or *.genmodel). Also,
with that approach, you could use qualified names to reference things,
without direct reference to a particular *.xcore or *.genmodel...

On 10/06/2014 6:09 AM, Christian Dietrich wrote:
> Hmm afaik xcore only indexes EClasses. (Check this with the open model
> element dialog) so you may change the grammar to
> Xxx=[score::EClass] or change xcores resource service provider (
> debug xvoreresourcedescriptionstrategy,)

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385711 is a reply to message #1385613]

Tue, 10 June 2014 15:56

Florian König

Messages: 30
Registered: June 2014

Member

Hi Christian,

Thanks for your suggestion! I tried that and changed some things, like this:

import "http ://www.eclipse.org/emf/2002/Ecore" as ecore

Import: 'import' importedNamespace=FqnWithWildCard;
FqnWithWildCard: Fqn('.*')?;
Fqn:ID('.'ID)*;

Select: 'select' class=[ecore::EClass | Fqn] name=ID;

This works, now I can select the classes I created in Xcore Smile

Like this:

selection test
{
	select org.test.RailCab
}

But I got two new Problems:

I get a lot of items I can put in there (and my Xcore classes even without an import), but I only want to have those I imported earlier in my import section. How can I do that?
When I select my RailCab class like the example above, I get this error: Quote:
Couldn't resolve reference to EClass 'org.test.RailCab'.

How can I fix these?

@Ed: Thanks to you too, but I don't really know how I can do that... Could you be a bit more specific?

Attachment: select railcab.png
(Size: 64.08KB, Downloaded 300 times)

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385714 is a reply to message #1385711]

Tue, 10 June 2014 16:03

Christian Dietrich

Messages: 14664
Registered: July 2009

Senior Member

Change back the grammar to xxx=[XXX|ID]

Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385761 is a reply to message #1385711]

Wed, 11 June 2014 05:56

Ed Merks

Messages: 33133
Registered: July 2009

Senior Member

Florian,

Comments below.

On 10/06/2014 5:56 PM, Florian König wrote:
> Hi Christian,
>
> Thanks for your suggestion! I tried that and changed some things, like this:
>
> import "http ://www.eclipse.org/emf/2002/Ecore" as ecore
>
> Import: 'import' importedNamespace=FqnWithWildCard;
> FqnWithWildCard: Fqn('.*')?;
> Fqn:ID('.'ID)*;
>
> Select: 'select' class=[ecore::EClass | Fqn] name=ID;
>
> This works, now I can select the classes I created in Xcore :)
> Like this:
> selection test
> {
> select org.test.RailCab
> }
>
> But I got two new Problems:
>
>
> I get a lot of items I can put in there (and my Xcore classes even without an import), but I only want to have those I imported earlier in my import section. How can I do that?
>
> When I select my RailCab class like the example above, I get this error: Quote:
>> Couldn't resolve reference to EClass 'org.test.RailCab'.
>
>
> How can I fix these?
>
> @Ed: Thanks to you too, but I don't really know how I can do that... Could you be a bit more specific?
I can only suggest you look at the Xcore grammar. I don't really know
your ultimate intent, but something to keep in mind. Xext grammar
language uses Ecore directly and relies on imports that specify the
nsURI of the Ecore model and then further relies on the index to index
all the *.ecore models, including *.xcore representations. But Ecore
models don't know about a fully qualified name just the name of the
package and the name of the classifiers (and structural features/enum
literals). So I'd not expect that approach to let you specify names
like org.test.RailCab. Xcore relies on indexing of all *.genmodel,
including *.xcore representations, and a GenClassifier knows about fully
qualified names in the sense of the generated Java code. So if you rely
on Xcore, you likely want your reference to be to a GenClassifier (or
perhaps more restrictively to be a GenClass). So try that instead of
EClass in your grammar.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385792 is a reply to message #1385761]

Wed, 11 June 2014 08:53

Hallvard Traetteberg

Messages: 673
Registered: July 2009
Location: Trondheim, Norway

Senior Member

Just a comment on using qualified names for EClasses. Doesn't the
standard QualifiedNameProvider create qualified names from the name
features of ENamedElements up to the root. Hence, most elements in an
Ecore model will get the qualified name you'd expect.

Hallvard

On 11.06.14 07:56, Ed Merks wrote:
> But Ecore
> models don't know about a fully qualified name just the name of the
> package and the name of the classifiers (and structural features/enum
> literals). So I'd not expect that approach to let you specify names
> like org.test.RailCab. Xcore relies on indexing of all *.genmodel,
> including *.xcore representations, and a GenClassifier knows about fully
> qualified names in the sense of the generated Java code. So if you rely
> on Xcore, you likely want your reference to be to a GenClassifier (or
> perhaps more restrictively to be a GenClass). So try that instead of
> EClass in your grammar.
>

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385796 is a reply to message #1385792]

Wed, 11 June 2014 09:19

Ed Merks

Messages: 33133
Registered: July 2009

Senior Member

Hallvard,

That would be the work of
org.eclipse.xtext.ecore.EcoreQualifiedNameProvider. I know that
org.eclipse.emf.codegen.ecore.xtext.GenModelQualifiedNameProvider does a
good job giving the actual name you'll see when you generate the code,
but for Ecore, you can only get up to the EPackage and that's not
generally a qualified name. I suppose, if you included parent packages
all the way up to "org" it would give a qualified name, but otherwise,
it's not ideal. And besides, if the focus on on referencing Xcore, then
there is a GenModel and the information is definitely well supported for
that (and would also work for a normal *.genmodel)...

On 11/06/2014 10:53 AM, Hallvard Trætteberg wrote:
> Just a comment on using qualified names for EClasses. Doesn't the
> standard QualifiedNameProvider create qualified names from the name
> features of ENamedElements up to the root. Hence, most elements in an
> Ecore model will get the qualified name you'd expect.
>
> Hallvard
>
> On 11.06.14 07:56, Ed Merks wrote:
>> But Ecore
>> models don't know about a fully qualified name just the name of the
>> package and the name of the classifiers (and structural features/enum
>> literals). So I'd not expect that approach to let you specify names
>> like org.test.RailCab. Xcore relies on indexing of all *.genmodel,
>> including *.xcore representations, and a GenClassifier knows about fully
>> qualified names in the sense of the generated Java code. So if you rely
>> on Xcore, you likely want your reference to be to a GenClassifier (or
>> perhaps more restrictively to be a GenClass). So try that instead of
>> EClass in your grammar.
>>
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: ScopeProvider with imported Xcore [message #1385845 is a reply to message #1385761]

Wed, 11 June 2014 15:39

Florian König

Messages: 30
Registered: June 2014

Member

Hi Ed,

Thank you very much! I would have been searching for this forever..
Now I changed some things, like this:

import "http://www.eclipse.org/emf/2002/GenModel" as genmodel 

Select: 'select' class=[genmodel::GenClass] name=ID;

This seems to work perfectly fine Smile

@Christian: Unfortunately changing it like xxx=[XXX|ID] did not work.

Report message to a moderator

Previous Topic:	Antlr update breaks workflow
Next Topic:	proper way to enrich model

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 08:00:23 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter