Eclipse Community Forums: TMF (Xtext) » [xtext] importUri is default when generating xtext project from existing ecore metamodels

Home » Modeling » TMF (Xtext) » [xtext] importUri is default when generating xtext project from existing ecore metamodels

[xtext] importUri is default when generating xtext project from existing ecore metamodels [message #885006]

Tue, 12 June 2012 04:53

Eclipse User

Hi

I am in the process of figuring out how to implement the importNamespace
starting with an Xcore model. When I generate the Xtext project form the
Ecore model then I notice that in the workflow:

// scoping and exporting API
fragment = scoping.ImportURIScopingFragment {}
fragment = exporting.SimpleNamesFragment {}

// scoping and exporting API

// fragment = scoping.ImportNamespacesScopingFragment {}
// fragment = exporting.QualifiedNamesFragment {}

Is there a reason for this?
Will I break something when I try to implement the importNamespace?

I will go on and see if importNamespace can be made to work and report back.

-H

Re: [xtext] importUri is default when generating xtext project from existing ecore metamodels [message #885067 is a reply to message #885006]

Tue, 12 June 2012 07:58

Eclipse User

The reason is that standard XMI - and this is likely where you come from
when using this wizard - usually uses URIs instead of names and scopes
to refer to other elements. It should not used anywhere and can be changed.

Am 12.06.12 10:53, schrieb Hugo A. Garica:
> Hi
>
> I am in the process of figuring out how to implement the importNamespace
> starting with an Xcore model. When I generate the Xtext project form the
> Ecore model then I notice that in the workflow:
>
> // scoping and exporting API
> fragment = scoping.ImportURIScopingFragment {}
> fragment = exporting.SimpleNamesFragment {}
>
> // scoping and exporting API
>
> // fragment = scoping.ImportNamespacesScopingFragment {}
> // fragment = exporting.QualifiedNamesFragment {}
>
> Is there a reason for this?
> Will I break something when I try to implement the importNamespace?
>
> I will go on and see if importNamespace can be made to work and report
> back.
>
> -H

--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com

Previous Topic:	[Xcore] derived feature and notification
Next Topic:	Scoping across multiple resources

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 03:34:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter