Bug 325305 - QVTo: Transformation events for usage data reporting and for tracking the artifacts involved (in, inout, out, trace, transfo)
Summary: QVTo: Transformation events for usage data reporting and for tracking the art...
Status: NEW
Alias: None
Product: QVTo
Classification: Modeling
Component: Engine (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-15 00:09 EDT by Nicolas Rouquette CLA
Modified: 2010-09-15 00:09 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Rouquette CLA 2010-09-15 00:09:39 EDT 
QVTo is a very powerful, versatile technology, so much so that it leads to a new class of problems, that of managing workflows that involve lots of QVTo operations.

Basically, the missing piece is a definition of a QVTO execution event that can be logged and that can be fed to the Eclipse usage data reporting system.

We may need 2 QVTO execution events:

1) a QVTo launch event created right before the execution of the QVTo transformation begins
- the URI of the QVTo transformation
- the URI of all transformation models provided (in, inout) and the URI of their metamodels
- the values of all transformation configuration parameters

2) a QVTo completion event created at the end of the  execution of a QVTo transformation
- the corresponding QVTo launch event
- execution status (normal completion, abnormal, exception)
- the URI of all of the transformation models modified or produced (i.e., inout, out, trace) and the URI of their metamodels