Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » [MWE] Some suggestions for MWE project
[MWE] Some suggestions for MWE project [message #137723] Fri, 26 June 2009 13:51
Nicolas is currently offline NicolasFriend
Messages: 6
Registered: July 2009
Junior Member
Hello,

Within the framework of the MoDisco project, we develop a plug-in
allowing initialize and execute a workflow of discoverers, generators
and model transformations.
MoDisco (The Model Discovery) is an Eclipse/GMT project on the
model-driven reverse-engineering. This project has for objective to
supply an Eclipse platform dedicated in model-driven
reverse-engineering: analyze quality, understanding of an existing
application, reverse-modeling, refactoring or migration
(http://www.eclipse.org/gmt/modisco/).
After comparison of the existing workflow projects, we concluded that
MWE is one of the best tool and the most promising one.

For that reason, we integrated it into our first version 0.1 of the
plug-in MoDiscoWorkflow. Nevertheless, we can not serialize the model
because the definition of the meta-model MWE prevents it to us.

To serialize the model and to be able to use it in external editors, we
propose you some modifications in the meta-model "workflow.ecore" to enrich.
Here is a non-exhaustive list of various points which were modified:
- We added the Root class to have an identified root in the meta-model.
Indeed actually, only a CompositeComponent can be a root element. We
could not thus have the definition of the components on the one hand and
workflow engine on the other hand in the same model.
- The class WorkflowUnitOfWork was abstract. It must be concrete to
represent the composite pattern within this meta-model. This
modification allows us to instantiate this class allowing us to have
simple components.
- We have also moved attribute “parameters” of the WorkflowUnitOfWork
class in the WorkflowComponent class because this attribute was also
available in the WorkflowCompositeComponent class
- The cardinality of the attribute “type” of the WorkflowParameter
class is now 0..1 because we consider that the type is not mandatory in
some case (default behavior = value of parameter can be an object).
- The cardinality of the attribute “connection” of the
WorkflowParameter class is now 0..1 because a parameter could have no
connections (example : entry and end points).
- The meta-model "workflow.ecore " is no more connected to the file "
Ecore.ecore ". It uses the Ecore model of EMF registered in EMF registry.

We created a post containing the patch for the
"org.eclipse.emf.mwe.ewm.core" project. This patch contains a new
definition of the "workflow.ecore " meta-model.
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=281657)

We already have a version 0.2 basing itself this time on the version of
modified MWE, also we would like to work with you to integrate the
aforesaid modifications. Of course we are open to all discussions in
order to integrate this patch to the project MWE.

Furthermore, we wish to create soon a graphical editor for MWE allowing
to modify an existing model and to integrate it into the MWE project (we
are testing GEMS and GMF possibilities).

Regards,

Nicolas Payneau
Previous Topic:Net4J Documentation
Next Topic:[MWE] Some suggestions for MWE project
Goto Forum:
  


Current Time: Sun Apr 14 19:53:36 GMT 2024

Powered by FUDForum. Page generated in 0.06724 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top