Bug 358814

Description Philipp Kalb 2011-09-25 06:13:46 EDT

Build Identifier: 20110615-0604

To put it in a nutshell: My transformation works if I debug it but it does not if I run it (with the same configuration and nothing in parallel).

The basic idea of the transformation-script is to transform two models(UML metamodel) into a common one (UML metamodel). I developed the script using the QVT editor and used it as shown in the "javaInvoke" example that I found in the m2m newsgroup. It actually works fine but the problem is that sometimes my transformed objects "forget" their classifiers.
So I changed the script and tried to run it via the "QVTEditor Eclipse plugin(s)". When I run it with "Run As..." I have classifiers in every 2 - 5 run, If I debug it they are always there.

I even added an "if" in the end of the transformation to check if the classifiers are null but the "if" is never true. When I run the transformation in a while loop that checks if the results are ok and if not run everything again, I get the right results after 2-5 runs. Its very random and time consuming..

So the problem appears when invoking it with java and when using the provided editor. 

This problem was described in the m2m newsgroup with title "[QVT] undeterministic behaviour". A similar problem was reported in the same newsgroup with the title "Invoke QVT In JAVA"


Reproducible: Sometimes

Steps to Reproduce:
1. create a transformation
2. write a simple application that invokes the script similar to the javaInvoke example. Such as:
/******************************************************************************/
//transformationURI link to qvt file
TransformationExecutor executor = new TransformationExecutor(transformationURI);

//inResource have the vaule of inModel
ModelExtent input = new BasicModelExtent(inResource.getContents());
ModelExtent output = new BasicModelExtent();

ExecutionContextImpl context = new ExecutionContextImpl();

ExecutionDiagnostic diagnostic = executor.execute(context, input, output);

/******************************************************************************/
3. run in several times in a loop