[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[News.eclipse.technology.mddi] Re: Do I understand MDDi?
|
Having read the whitepaper and the answers here I would like to
recapitulate.
Correct me if I'm wrong.
> On one hand it sounds like a modeling tool platform where different
> modelling tools and pluged in via adaptors, much the same way that eclipse
> lets you combine text editors, source control and compilers. The various
> tools could then be used in a consistent manner irrespective of thier
> underlying protocol.
This is what the Model Bus is for. It will be a server running independently
of Eclipse, contacted by WSDL/RMI
There will be an Eclipse plugin to contact a Model Bus Server.
> On the other hand it sounds like a scriptable build tool for orchistrating
> these mda scenarios, lets say an Ant for MDA. I currently do something
> along
> these line using Jelly and my own custom tags for executing
> transformations
> and code generators. In time I was looking to create a uml profile for
> modelling the build process and then generating the script. Is this
> something MDDi would do?
There will be a MDA scenario description language on top of the Model Bus,
coordinating the tools plugged in.
Is this inside the scope of the project? Is there a whitepaper? This would
also require a SDK plugin for programming the MDDI server remotely.
Have I got it right?