Thank you very much, Hugo.
I ended up with this piece of code (let me know if you consider it appropriated):

try
{
//AtlVM.getVM(vm).launch(asmUrl, libs, models, params, superimps, options);
//AtlLauncher.getDefault().launch(asmUrl, libs, models, params, superimps, options);
ASM asm = new ASMXMLReader().read(new BufferedInputStream(asmUrl.openStream())); superimps.add(0, asm); //New ILauncher.launch(..) method takes a list of modules where the first module of the set is overriden by the next ones
ILauncher atlL = CoreService.getLauncher(ATLLaunchConstants.REGULAR_VM_NAME); atlL.launch(ILauncher.RUN_MODE, new NullProgressMonitor(), options, superimps);
} catch (IOException e)
{
ATLLogger.log(Level.SEVERE, e.getLocalizedMessage(), e);
} catch (ATLCoreException e) {
ATLLogger.log(Level.SEVERE, e.getLocalizedMessage(), e);
e.printStackTrace();
}

I will do a partial test of my refactorization with an AMW refactorization I'm also performing (it may take a while, though, as I have other thing in hand).
Perhaps (if you already have test suites for AM3) you may like me to send it to you so you could start testing it already?. Just let me know.

How is everyone in EDM-Nantes?, send my regards.
Merçi ;-),

Everything goes well at EMN. Thanks!

Cheers,

Hugo

              Juan Pedro

Hugo Bruneliere escribió:

Hi Juan,

Juan Pedro Silva a écrit :

Hi Hugo, thank you for your support.
If I take the mentioned approach, the following instruction:

AtlVM.getVM(vm).launch(asmUrl, libs, models, params, superimps, options);

Is no longer supported (AtlVM is no longer there in ATL 3.0), so I need a suggestion in how to rewrite that instruction.
These alternatives might work, but not sure which is best:

RegularVMLauncher.launch(java.lang.String mode,
org.eclipse.core.runtime.IProgressMonitor monitor,
java.util.Map<java.lang.String,java.lang.Object> options,
java.lang.Object... modules);

or

AtlLauncher.getDefault().launch(java.net.URL asmurl, java.util.Map libraries, java.util.Map models, java.util.Map asmParams, java.util.List superimpose, java.util.Map options)

The first alternative is using the regular VM, but parameters are not the same, and as documentation is scarce, I don't know how to convert them.
On the other side, the second alternative takes the same parameters, but my feeling is that it will use the new VM (as it is the default one), and not regular VM.
There may be other (more correct) alternatives, but I'm not acquainted with the new API, and those are the ones I found so far.
Do you have any suggestions for this instruction?.

In order to get the launcher of the Regular VM (but which conforms to the new ILauncher interface), you can use the "getLauncher()" method of the org.eclipse.m2m.atl.core.service.CoreService class:

ILauncher atlLauncher = CoreService.getLauncher(ATLLaunchConstants.REGULAR_VM_NAME);
//of course, ATLLaunchConstants.EMF_VM_NAME also exists
atlLauncher.launch(...);
Cheers,

Hugo

I'll love to contribute once I finish refactoring.
Thanks for your help.
Regards,
              Juan Pedro

Hugo Bruneliere escribió:

Hi Juan,

First, thank you very much for your contribution. I'm sure it will be used by many AM3 & ATL developers :-)

Juan Pedro Silva a écrit :

Hi everybody, I'm trying to rewrite some parts of AM3's deprecated packages branch to use ATL 3.0.
I have managed to modify most parts to use the new API, but I have doubts on a particular piece of code.
The code in hands is in class org.eclipse.gmt.am3.tools.ant.ATLModelTransformationTask, and is this one:

...
if(vm == null)
vm = AtlVM.ATLVM_REGULAR; ...
if (!debug.booleanValue())
AtlVM.getVM(vm).launch(asmUrl, libs, models, params, superimps, options);
...

I guess I can rewrite the first red line as
           vm = ATLLaunchConstants.REGULAR_VM_NAME;

but I don't believe this is the correct way to go, I think I should change the structure somehow.
Can anyone give me a pointer on this?.

From my point of view, what you propose is good because it keeps exactly the same behavior as the previous version. I don't think it is necessary to modify the current structure of the plugin, at least in a first time.

Of course, it would be great if you could contribute your upgrades by submitting a patch via Bugzilla!

Cheers,

Hugo

Thanks,
            Juan Pedro

--
-------------------------------------------------
Hugo Bruneliere - R&D Engineer
AtlanMod research team (INRIA & EMN) - Room B206
École des Mines de Nantes
4, rue Alfred Kastler
44307 Nantes Cedex 3 - France
Office: +33 (0)2 51 85 82 21
EMail: hugo.bruneliere@xxxxxxxx
-------------------------------------------------

this is a nice initiative!!

I haven't worked with the ATL 3.0 API so far, I have just used ATL 2.x
versions, to keep compatibility. I have some comments below.

ASMEMFModel.getResourceSet()

ASMEMFModel.loadASMEMFModel(...) -> is EMFModelLoader.loadModel(..)

equivalent?

For loading models, you just need to get an EMF model in return, so
EMFModelLoader.loadModel(..) should be OK.

ASMEMFModel.createMOF(modelLoader) -> you can always do emfModelLoader.getMOF(), or ASMEMFModel.getMOF(), but I'm n ot sure if any

those is semantically the same (the first one having more chances).

The two last ones are probably facilities to get the MOF (which is
actually EMF) metametamodel directly, so you could use them as well.

I'm also refactoring the AM3 deprecated branch to use this new API. I changed

I have done some modifications recently in the code to remove these
dependencies in the AMW code. This simplifies the installation process.
I do a dynamic class load of KM3Injector and Projector. You may take
advantage of that change.

Also, there might be incompatibilities between ATL 3.0 and AMW that I might

be missing.

Once finished (and tested), it may be a possibility to contribute to
the AMW code, for instance, buy proposing a patch through Bugzilla.

Regards,

Marcos.

Fabien.

I am totally new to model transformations. I want to implement the tranformation and model weaving using the eclipse IDE. Fortunately, I found a usecase on eclipse website which resembles my requirements of transforming from RDBMS to XML. This usecase is:
http://www.eclipse.org/gmt/amw/usecases/RDBMSXML/

But unfortunately even after trying for long time I am unable to install the eclipse and the required plugins to see the same UI as shown in the usecase or as described on the webpage http://wiki.eclipse.org/index.php/AMW. I have followed the instructions on the eclipse website to install the following:

1. Eclipse 3.4.2 (Eclipse Ganymede)
2. EMF 2.4.0
3. UML2 2.2
4. ATL dev 2_1_0
5. AM3 dev
6. mwplugins-20061208.zip

Also followed the instructions on the webpage:
http://www.eclipse.org/gmt/amw/download/

First of all, I am getting an error:
Bundle 'org.eclipse.gmt.tcs.dsls' cannot be resolved - MANIFEST.MF - org.eclipse.gmt.am3.dsls.km3/META-INF - line 14 Plug-in Problem

I am unable to get rid of this error. And also I can niether see the perspective Model weaver nor perspective AM3 as described in many of the examples.

Can anybody please help?? I will be highly obliged.

Thanks and regards,

Vikas

Vikas

I have tested with the following versions:

Regards,

Marcos.

Regards,

Marcos.

Thanks