Eclipse Community Forums: QVT-OML » Obtain URI from evaluation environment in RC4

Home

Home » Modeling » QVT-OML » Obtain URI from evaluation environment in RC4

Obtain URI from evaluation environment in RC4 [message #1385848]

Wed, 11 June 2014 11:51

Eclipse User

Hello,

With Kepler it was possible to obtain the resource URI from the evaluation env as such:

QvtOperationalEvaluationEnv evalEnv = (QvtOperationalEvaluationEnv) getEvaluationEnvironment();
InternalEvaluationEnv internEnv = evalEnv.getAdapter(InternalEvaluationEnv.class);

Module module = internEnv.getCurrentModule().getModule();
URI compiledUri = module.eResource().getURI(); // .qvtox

This no longer works with Luna, since URIs all show up as "qvto:/module.env".

Does anyone know how to get a URI (or anything representing the physical transformation) from the evaluation environment? Specifically I'm working from within a derived QvtGenericVisitorDecorator.

Thank you for any direction,
Chris

Re: Obtain URI from evaluation environment in RC4 [message #1385928 is a reply to message #1385848]

Thu, 12 June 2014 05:58

Eclipse User

Hi Christine

Unhelpful answer: Internal ... is internal so it might change.

Realistically, I don't think it should have changed so please raise a
Bugzilla.

Anything with an AST node will do. Perjhaps your invoking
context/visitor has more to go on. Perhaps
evalEnv.getOperation().eResource().

Regards

Ed Willink

On 11/06/2014 16:51, Christine Gerpheide wrote:
> Hello,
>
> With Kepler it was possible to obtain the resource URI from the
> evaluation env as such:
>
> QvtOperationalEvaluationEnv evalEnv = (QvtOperationalEvaluationEnv)
> getEvaluationEnvironment();
> InternalEvaluationEnv internEnv =
> evalEnv.getAdapter(InternalEvaluationEnv.class);
>
> Module module = internEnv.getCurrentModule().getModule();
> URI compiledUri = module.eResource().getURI(); // .qvtox
>
> This no longer works with Luna, since URIs all show up as
> "qvto:/module.env".
>
> Does anyone know how to get a URI (or anything representing the
> physical transformation) from the evaluation environment? Specifically
> I'm working from within a derived QvtGenericVisitorDecorator.
>
> Thank you for any direction,
> Chris
>
>

Re: Obtain URI from evaluation environment in RC4 [message #1386104 is a reply to message #1385848]

Fri, 13 June 2014 08:36

Eclipse User

Hi Christine,

Christine Gerpheide wrote on Wed, 11 June 2014 11:51

With Kepler it was possible to obtain the resource URI from the evaluation env as such:
QvtOperationalEvaluationEnv evalEnv = (QvtOperationalEvaluationEnv) getEvaluationEnvironment();
InternalEvaluationEnv internEnv = evalEnv.getAdapter(InternalEvaluationEnv.class);

Module module = internEnv.getCurrentModule().getModule();
URI compiledUri = module.eResource().getURI(); // .qvtox
This no longer works with Luna, since URIs all show up as "qvto:/module.env".

On the runtime the result of the expression 'module.eResource().getURI()' is always "qvto:/module.env" and was not changed between Luna/Kepler/Juno releases.
You probably mixed up it with the JUnit tests execution where 'TransformTests.interpreterSuite()' performs saving of compiled transformation to .qvtox file later loading it and performing the execution of the restored transformation. In JUnit this is done solely for testing purpose.
Anyway it's not correct to utilize internal knowledge that the Module instance is contained by EMF Resource.

Quote:

Does anyone know how to get a URI (or anything representing the physical transformation) from the evaluation environment? Specifically I'm working from within a derived QvtGenericVisitorDecorator.

Try the code below:

InternalEvaluationEnv internEvalEnv = getOperationalEvaluationEnv().getAdapter(InternalEvaluationEnv.class);
Module currentModule = internEvalEnv.getCurrentModule().getModule();
IModuleSourceInfo moduleSource = ASTBindingHelper.getModuleSourceBinding(currentModule);
URI moduleUri = null;
if(moduleSource != null) {
	moduleUri = moduleSource.getSourceURI().appendFragment(currentModule.getName());
}

Note the usage of '.appendFragment()'. This is due to fact that single .qvto source may contain several transformations (see http://git.eclipse.org/c/mmt/org.eclipse.qvto.git/tree/tests/org.eclipse.m2m.tests.qvt.oml/parserTestData/models/bug416584/bug416584.qvto).

Regards,
Sergey.

Previous Topic:	How to use QVTo transformation
Next Topic:	How to evaluate OCL expression that is part of the input model

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 05:01:29 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter