Skip to main content
Jump to: navigation, search

Difference between revisions of "QVTo/New and Noteworthy/Helios"

Line 34: Line 34:
The milestone was completed on Tuesday, 10 November 2009
The milestone was completed on Tuesday, 10 November 2009
[ 291458] Content viewer for QVTo concrete syntax files
[ 291458] Content viewer for QVTo concrete syntax files
Line 42: Line 44:
The milestone was completed on Wednesday, 16 December 2009
The milestone was completed on Wednesday, 16 December 2009
[ 290002] QVTo parser model (CST model) adopted to OCL parser model
[ 290002] QVTo parser model (CST model) adopted to OCL parser model

Revision as of 15:02, 27 May 2010

Milestone 2

The milestone was completed on Wednesday, 30 September 2009


204085 XMI serialization of AST models created by the QVTo parser

256149 Contextual operation in Java black-box library as non-static Java method

267493 UI creation wizard for QVTo Ant tasks

284989 QVTo Invocation API now handles dynamic models

285007 Semantic highlighting to QVTo editor

287589 Performance improvement of trace generation and look up

287594 Direct support for 'nullable' enumerations


287711 Input EObjects having eContainer != null can't be accessed as model extent root objects

Now QVTo supports use-case when user pass EObjects that are children of an existing object tree as input to QVTo transformation execution. As a consequence input EObjects having
eContainer != null
are now correctly returned by the following call:
transformation ClassesTransf(inout model : UML20);
main() {
   var classes := model.objects()[uml20::classes::Class];

Milestone 3

The milestone was completed on Tuesday, 10 November 2009


291458 Content viewer for QVTo concrete syntax files

QVTo specific syntax highlighting viewer is available in Compare, Merge views.

Milestone 4

The milestone was completed on Wednesday, 16 December 2009


290002 QVTo parser model (CST model) adopted to OCL parser model

OCL grammar has been substantially revised to align with the likely OCL 2.1 specification. Since QVTo grammar is based on OCL is was necessary to modify QVTo LPG grammar to stay in sync with it.


295060 Transformation executor must accept a generic transformation URI

Transformation executor (described here Executing QVTo transformations from Java) now accepts all kind of URI schemes generally accepted by EMF resource implementation (like file:/.., etc.).

Debug facility

In M4 QVTo Debug tooling was implemented (QVTo debugger runs on top of Eclipse debugging framework, source lookup mechanism). It provides basic debug features:

* breakpoints
* StepOver, StepIn, StepOut, Run to Line
* variables view
* expressions view
* watches

Some bugzillas related to this new QVTo Debug configuration:

295844 Implement concept of debuggable QVT Virtual Machine
295845 Provide QVT debug core implementation
296633 Provide debug.ui implementation

QVTo remote debug launch configuration page (provides all standart Eclipse Application configurations pages). It allows to debug Java black-box implementation along with QVTo script in one workspace:


QVTo workspace debug launch configuration page (only Transformation and Configuration Properties pages). Allows to debug QVTo script right in working workspace:


Sample of QVTo debug process with all standard debug facilities (conditional breakpoints written in QVTo are supported as well):


Milestone 5

The milestone was completed on Tuesday, 2 February 2010


287685 Support for standalone QVTO execution

Now transformation can be invoked outside Eclipse from Java via org.eclipse.m2m.qvt.oml.TransformationExecutor (see Executing QVTo transformations from Java.

Required dependencies:

//-- EMF and OCL jars ----------
//-- QVTo jars ----------

For package (metamodel) registry, resource factories initialization see EMF use in standalone applications

287714 Revise excessive checking for [inout] and [out] transformation parameter types

Now QVTo support custom EMF resource implementations, such as cdo:// etc. resources, as transformation [inout/out] parameters. Before these changes such inputs were only available for [in] parameter types.

LPG v2.0.17 adoption

Parsing infrastructure has been changed so that now it relies on LPG v2.0.17. Reasons behind that decision are that LPG v1.x is stated to be deprecated and also that LPG v1.x run-time has some deficiencies relating performance and memory usage.

297966 QVTo grammar is aligned to LPGv2

300560 Reintroducing official LPGv2 templates

Milestone 6

The milestone was completed on Tuesday, 16 March 2010


302592 New _ (underscore) prefix policies

Now parser supports _'xxx' name escaping policy (along with old _xxx).

Milestone 7

The milestone was completed on Tuesday, 4 May 2010


308049 Accessing Eclipse console from QVTo black-box library

Java black-box implementation now has a mean to access QVTo execution context so transformation configuration properties and standard logging capability are available.

Sample of Java black-box library methods that are declared to have an access to QVTo execution context:

@Operation (kind=Kind.HELPER, withExecutionContext=true)
public void logToConsole(org.eclipse.m2m.qvt.oml.util.IContext context, String param) {
@Operation (withExecutionContext=true)
public void cancelExecution(org.eclipse.m2m.qvt.oml.util.IContext context) {
@Operation (contextual=true, withExecutionContext=true)
public String getConfigProperty(org.eclipse.m2m.qvt.oml.util.IContext context, String strContext) {
	return context.getConfigProperty(strContext).toString();

Sample invocation of the methods above from QVTo script:

main() {
	logToConsole('console output from blackbox lib');

Back to the top