|Re: [QVTO] trace file [message #513310 is a reply to message #512673]
||Tue, 09 February 2010 17:52
| Sergey Boyko
Registered: July 2009
Hi mariam ,|
Some replies are in-lined below.
> I am having a problem understanding how trace files are generated in qvto.
> I think it is automatically generated when the transformation has in and
> out models. But what about in-place transformations ? Is there a way to
> generate a trace file of the executed mappings ?
Trace is generated automatically upon executing transformation.
Transformation signature (any combination of [in]/[inout]/[out] models,
even empty list) does not matter - trace is always filled with the list
of mappings being executed.
Trace is utilized by resolve*() functions. When transformation finishes
trace is saved to trace file (.trace by default) if specified in launch
> Another question, can we control what information is stored in the trace
> file. As far as I know, it only stores a list of mappings that were
> applied during the transformation.
No, there's no possibility to save addition information to trace.
> But what if i also want to store the values of some parameters and the
> context on which these mappings were applied.. Is that possible ?
Unfortunately you have to maintain custom trace-like model for that.
Also you can make use of 'eAnnotations' property for example on
instances modified by transformation.
> Is there any link explaining this, or any examples ?
Creation of trace records is explained in Section 126.96.36.199 Mapping
Operation, Execution Semantics of QVT specification.
> Thanks a lot
Powered by FUDForum
. Page generated in 0.06485 seconds