Eclipse Community Forums: Epsilon

Help

Home

Home » Modeling » Epsilon » EGL imports(EGL imports)

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

EGL imports [message #1226440]

Wed, 01 January 2014 20:14

Arseniy Isakov

Messages: 118
Registered: May 2012

Senior Member

Hello

I have following egl template

[%

import "common/typePointer.eol";

var util := new Native("org.tura.metamodel.commons.Util");

if (model_mapper.getQueries().size()<> 0) {
var query = model_mapper.getQueries().get(0);
var type = util.runQuery(query,model_mapper);

var remoteInterface : Template = TemplateFactory.load("remoteInterface.egl");
remoteInterface.generate(type.getMappedJavaType() + ".java");

}
%]

Seems like import for EGL is not working.
Can you please help me to resolve the problem.
Thanks
Arseniy Isakov

Report message to a moderator

Re: EGL imports [message #1226462 is a reply to message #1226440]

Wed, 01 January 2014 21:38

Arseniy Isakov

Messages: 118
Registered: May 2012

Senior Member

I figured out my mistake I have to define relative path in my imports
import "../../commons/typeElementUtil.eol";
But this solution is not very useful because if I move my egl template to another location I have to modify my imports
If I use following :
import "/commons/typeElementUtil.eol";
I am getting an error

Report message to a moderator

Re: EGL imports [message #1226608 is a reply to message #1226462]

Thu, 02 January 2014 07:29

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

The EMF way is to operate relative to the virtual "platform:". Have you
tried "platform:/project/....."

Relative paths should work stably if you go up to platform: and down again.

Regards

Ed Willink

On 01/01/2014 21:38, Arseniy Isakov wrote:
> I figured out my mistake I have to define relative path in my imports
> import "../../commons/typeElementUtil.eol";
> But this solution is not very useful because if I move my egl template
> to another location I have to modify my imports
> If I use following :
> import "/commons/typeElementUtil.eol";
> I am getting an error

Report message to a moderator

Re: EGL imports [message #1227024 is a reply to message #1226608]

Fri, 03 January 2014 10:23

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi 
 
Apologies. A misleading email to start the new year. 
 
You should of course try "platform:/resource/project/....."
for workspace content and "platform:/plugin/bundle/....."
for installed plugin content. 
 
 Regards 
 
 Ed Willink 
 
 
On 02/01/2014 07:29, Ed Willink wrote: 
</div>
<blockquote cite="mid:la34hi$5lj$1@xxxxxxxxe.org" type="cite">Hi
 
 
The EMF way is to operate relative to the virtual "platform:".
Have you tried "platform:/project/....."
 
 
Relative paths should work stably if you go up to platform: and
down again.
 
 
 Regards
 
 
 Ed Willink
 
 
 
On 01/01/2014 21:38, Arseniy Isakov wrote:
 
<blockquote type="cite">I figured out my mistake I have to define
relative path in my imports
 
import "../../commons/typeElementUtil.eol";
 
But this solution is not very useful because if I move my egl
template to another location I have to modify my imports
 
If I use following :
 
import "/commons/typeElementUtil.eol";
 
I am getting an error </blockquote>
 
</blockquote>
 
</body>
</html>

Report message to a moderator

Re: EGL imports [message #1227073 is a reply to message #1226608]

Fri, 03 January 2014 13:04

Arseniy Isakov

Messages: 118
Registered: May 2012

Senior Member

This is code from EolImport

// Useful for plugin developers: fall back on platform:/resource if platform:/plugin does not work
if ("platform".equals(uri.getScheme()) && uri.getPath().startsWith("/plugin/")) {
final String sNewURI = uri.toString().replaceFirst("/plugin/", "/resource/");
uri = new URI(sNewURI);
importedModule.parse(uri);

According this logic path has to be
import "platform:/plugin/commons/typeElementUtil.eol";

But first eclipse editor gives you parsing error
second it is trying to locate platform:/resources/commons/typeElementUtil.eol which is not exists because bundle has /commons/typeElementUtil.eol

Report message to a moderator

Re: EGL imports [message #1227187 is a reply to message #1227073]

Fri, 03 January 2014 20:03

Antonio Garcia-Dominguez

Messages: 594
Registered: January 2010
Location: Birmingham, UK

Senior Member

As Ed Willink said, you need to add the name of your plugin. Try this:

import "platform:/plugin/name.of.your.plugin/path/within/your/plugin";

This Eclipse help page might be useful:

http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fplatform-scheme-uri.html

Report message to a moderator

Re: EGL imports [message #1227247 is a reply to message #1227187]

Sat, 04 January 2014 00:12

Arseniy Isakov

Messages: 118
Registered: May 2012

Senior Member

yes it works.
Thanks
Arseniy Isakov

Report message to a moderator

Previous Topic:	EGL Native class instantiation
Next Topic:	EGL and User defined operation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 05:15:29 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter