Eclipse Community Forums: QVT-OML

Home » Modeling » QVT-OML » Compiled output(A way for compiling and load/save processed compiler output)

Sun, 28 November 2021 06:38

Eclipse User

Hi all,

I've checked inside QVT, I've seen that the result of QVT-compiler is an output file. More or less as Acceleo does.

I'm executing the transformation as a standalone application; coudl I load these files when executing my transformation?
If it were possible, what is the best way (in your opinion) for storing "qvtox" files after compiler?

Thank you guys for your help.
Fabio.

Re: Compiled output [message #1848331 is a reply to message #1848328]

Sun, 28 November 2021 07:57

Eclipse User

Hi

(More rather than less since both Acceleo and QVTo rely on serializing the pragmatic implementation of the Classic Eclipse OCL Abstract Syntax Tree; a necessary but non-standard approach given the inadequacy of the OCL specification.)

Since the inter-release stability of the serialization is dubious, the QVTo project has not struggled to isolate build and execute phases, so at the Eclipse IDE level there is no ability to save or load *.qvtox files. However if you use the underlying Java API you can intercept the compile/execute boundary to save and load as you see fit; just be warned that persisting *.qvtox files across QVTo releases may sometimes fail.

Regards

Ed Willink

Re: Compiled output [message #1848338 is a reply to message #1848331]

Sun, 28 November 2021 16:57

Eclipse User

Thank you for the advice and your support

Fabio.

Re: Compiled output [message #1848358 is a reply to message #1848328]

Mon, 29 November 2021 10:14

Eclipse User

Hi Fabio

Fabio Popcorn wrote on Sun, 28 November 2021 06:38

I'm executing the transformation as a standalone application; coudl I load these files when executing my transformation?

Yes in general, the TransformationExecutor supports loading *.qvtox files. However there is no need to do so because the QVTo compiler is part of the standalone environment. Thus you can just load the *.qvto file, thereby compiling and caching your transformation for subsequent executions. By loading *.qvtox instead, you save just one compilation at runtime, nothing more.

Kind regards
Christopher

Previous Topic:	Element is not transformed inside its container
Next Topic:	QVTo disjunct operation on abstract mappings

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Nov 09 18:36:03 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter