I would like to use MTL for specifying some transformations as part of the
Eclipse project Java Workflow Tooling (JWT).
In ATL I have the problem that I didn't find a possibility to navigate
through some package structures and create as a target a workflow file
that contains the packages from the source file in the same structuring.
Since MTL is now a standard by the OMG, I thought I might better switch to
MTL in order to create my transformations and solve this problem.
Since the wiki pages are not really up to date and there is not much
documentation available (besides the ESE08 presentation which I attended
in Ludwigsburg), I would like to ask:
-what is the current status of the project (stable, all aspects of the OMG
-whether the described package navigation is possible in MTL?
Thanks in advance for your assistance and best regards,
imagine a metamodel with the following structure:
Main package "A" with two sub-packages "A1" and "A2". Another main package
"B" with sub-package "B1". I would like to have a transformation from that
model into exactly the same model with the same package structure. In ATL
I only found a possibility to specify a rule which works for package in
general (e.g. rule Package2Package), but this rule then applies for all
packages found in the source model. Therefore, my target model would have
five main packages (A, A1, A2, B and B1), whereas my source model only had
Does MTL take care of such packaging structure? Maybe you might show me a
link where this is described in detail?
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
I'm not sure what you're trying to achieve. You do know MTL is a model
to text technology as opposed to ATL that is a model to model? Was
wondering because of your mention of ATl and a "target model".
Nevertheless, if what you're trying to do is generating text from your
model, you can indeed take into account the package hierarchy when
generating your files. The only available documentation is the OMG MTL