Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mddi-dev] Acceleo team - MDR2EMF translator contribution 
Hi Stéphane,

That sounds great. We currently support only a limited set of XMI flavors and we need to enhance
this to improve interoperability among modeling tools.

The next step is to find out how to integrate the current ModelBus serializers with the bridges
mentioned below. Do you guys (from LIP6 or Obeo) have an idea of how to proceed?

Thanks,

Sébastien

Stéphane LACRAMPE a écrit :

  Hi All,
Following the last Mddi meeting, I would like to propose the following contribution to the Mddi community. 

_*Introduction :*_
In the context of the Acceleo project (http://www.acceleo.org), we have developed a MDR to EMF bridge for UML models. It can deal with UML 1.x XMI 1.x models and to transform them into EMF based models. It's especially useful for improving interoperability with the main UML modelers on the market. Here are some example of supported modelers with this bridge : AgoUML, Poseidon, Sparks EA, MagicDraw, Rose... The bridge would come in the ModelBus code base and would be quite useful to help to solve XMI interoperability issues. 
*_
General description :_*
The bridge is based on the MDR framework (NetBeans project), which means that XMI input files are read using the MDR framework and JMI standard. An XMI file representing an exported UML1.x model can be converted into another XMI file based on UML1.x model for EMF. A conversion is executed at the meta-level, permitting, for example, the conversion of a UML 1.3 / XMI 1.2 model into a UML 1.3 / XMI 2.0 model, which is can be directly used with EMF. The bridge includes UML 1.3 and UML1.4 metamodels implementations for EMF (others can be developed). 

_*Process :*_
Currently, there are two ways to use the bridge :
- either you right-click on the exported XMI file and launch "Convert to EMF". 
 - or you use the Acceleo chain system to kick it of automatically
A new file with the extension "uml13" (or "uml14") is created along side of the selected file. 
An extension for ModelBus would be suitable.
_*
Technical architecture :*_
There are 4 plugins included in this bridge :
- fr.obeo.acceleo.bridge.ui : UI plugin that contains the action to convert MDR files. - fr.obeo.acceleo.bridge : plugin that defines the MDR repository facade for UML 1.3 and UML 1.4. There is a reflective introspection on MDR objects to create EMF objects in the output model. - fr.obeo.acceleo.uml13 : An EMF representation of the uml13 metamodel. The URI of this metamodel is "http://www.obeo.fr/acceleo/uml13";. - fr.obeo.acceleo.uml14 : An EMF representation of the uml14 metamodel. The URI of this metamodel is "http://www.obeo.fr/acceleo/uml14";.
The benefit for Mddi is to be able to provide an improved interoperability of the eclipse platform with current market modelers. The benefit for Acceleo is to improve this bridge for others metamodels or others unsupported non-EMF modelers. Our goal is also to join the Mddi project with this submission and to share development. 

Please let me know if you have any question or comment.

Thanks,

Stéphane

_______________________________________________
mddi-dev mailing list
mddi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mddi-dev

Back to the top