[news.eclipse.modeling.tmf] Re: Domain model example: Proposal with enti

[Knut Wannheden <knut.wannheden@xxxxxxxxxx>]

Hi Ilyas,

Indeed it looks like a reference in your model cannot be linked. Thus there is 
probably a problem with your scope provider. Please provide more details 
(grammar, scope provider implementation, and example) so we can help you 
resolve the problem.

Regards,

--knut

Ilyas Keser wrote:
> Hi,
>
> in all workflows the standalone setup registers all used ecore 
> metamodels. Additionally in workflows for language generation the 
> EcoreGeneratorFragment refers to required genmodels. And language 
> generation works for my all DSLs... But, if I try to run the 
> MyDslGenerator.mwe the references to "Attributes" can't be resolved:
>
>     ERROR eclipse.emf.mwe.core.WorkflowRunner .. "Couldn't resolve 
> reference to Attribute".
> I am using a custom scoping to get a modified content assist for 
> Attributes (for example: org.my.package.MyClass.myAttribute instead of 
> myAttribute). Can this error be related with my custom scoping? Or do I 
> need to modify the linking mechanism of Xtext. I don't really understand 
> (out of the documentation) when a custom linking mechanism is needed. 
> Thanks,
> ILyas
>
>
>
> Sebastian Zarnekow schrieb:
> > Hi Ilyas,
> >
> > basically you'll have to register every references ecore metamodel in 
> > the standalone setup. The type of your uris in your grammar has 
> > nothing to do with the runtime or the fact that you have to register 
> > metamodels in the standalone setup.
> > Please refer the EMF book to get used to the various EMF concepts.
> >
> > Regards,
> > Sebastian