Hi
To
be honest, I’m unhappy with the resolution of
QVT13-22.
The
QVT13-23
resolution
implies that there is a trace record for every mapping
execution, “but not those by transformation invocations”.
That’s exactly what this issue is about. If there are no
trace records for mappings executed inside an accessed
transformation, the entire trace of the accessed
transformation gets lost after its termination. This reduces
the possibilities for transformation composition: if I need
full traceability, I can’t decompose my transformation into
subparts, and vice versa. However if I have a stepwise
transformation with intermediate models, I’m actually
dependent on “accessing” sub-transformations (intermediate
models won’t work otherwise). I’m actually suffering from
exactly this dilemma with one of my transformations where I
need full traceability.
I
agree that, due to parallelTransform(), an accessed
transformation shouldn’t reuse the trace data of the
accessing transformation. But why is there no write-back
after the termination of transform() or parallelTransform()
? Exposing a trace is often useful and never hurts.
In
any case, the resolution text is somewhat contradictive:
there are trace records for accessed transformations, but
not for transformation invocations. That’s a contradiction,
because an accessed transformation must always be invoked
explicitly.
Kind
regards
Christopher