[Epsilon] Standalone: imported sources [message #669283] |
Mon, 09 May 2011 13:56  |
Eclipse User |
|
|
|
Hello,
I am running Epsilon standalone with a set of classes based on the exampled found in the repository. I have successfully ran eol, evl and egl sources. However when running a etl source something went wrong. I get no parsing errors and no execution errors, but the generated models are empty. I have ran this etl not in standalone and it works fine, i.e. models are generated ok. The only reason I can think of is the use of an import statement in my etl source:
///
/// This file contains the transformation rules to transform the structural
/// part of the SysML model to its representation in HiLeS.
import "SysMLModelQueries.eol"; // SysML model queries
...
When running the etl source from eclipse, the eol file is in the same location as my etl file.
My standalone application is a set of eclipse plugins. One plugin holds all the epsilon stand alone classes, and other plugins reference it for specific model operations. Since the etl, eol, egl, etc., sources are packaged with the latter set of plugin, I use the platform:plugin URI scheme to locate them and load them to the epsilon respective module. This can be seen next:
...
EtlExecutor etlExecutor;
try {
etlExecutor = new EtlExecutor("platform:plugin/co.edu.uniandes.hiles.sysml/src/co/edu/uniandes/hiles/sysml/SysML2HilesStructure.etl");
} catch (URISyntaxException e) {
console.errln("GRAVE Error: Loading SysML to HiLeS transformation source failed. Please verify plugin instalation.");
e.printStackTrace();
return this;
}
So my questions are: In this case, where does the etl(eol) module expect to find the imported resources? Is there a mechanism to load the imported resources to the module? Should I change the import string to a complete URI?
Regards,
Horacio Hoyos
|
|
|
|
|
Re: [Epsilon] Standalone: imported sources [message #669817 is a reply to message #669575] |
Wed, 11 May 2011 11:57  |
Eclipse User |
|
|
|
Antonio,
Your observation was correct! Thanks very much, now I use the "normal" import statement and everything works.
Best regards,
Horacio
P.D. Next test is with ECL and EML... I think passing the ECL trace into the EML module will definitely bring me back to the forums.
|
|
|
Powered by
FUDForum. Page generated in 0.03856 seconds