Unhelpful answer: Internal ... is internal so it might change.
Realistically, I don't think it should have changed so please raise a
Anything with an AST node will do. Perjhaps your invoking
context/visitor has more to go on. Perhaps
On 11/06/2014 16:51, Christine Gerpheide wrote:
> With Kepler it was possible to obtain the resource URI from the
> evaluation env as such:
> QvtOperationalEvaluationEnv evalEnv = (QvtOperationalEvaluationEnv)
> InternalEvaluationEnv internEnv =
> Module module = internEnv.getCurrentModule().getModule();
> URI compiledUri = module.eResource().getURI(); // .qvtox
> This no longer works with Luna, since URIs all show up as
> 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,
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.
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.