[news.eclipse.modeling.mdt.uml2] Re: Strategy for loading commercial UML

[Dawid Loubser <dawidl@xxxxxxxxxxx>]

Thank you so much for your response Vlad, even though it is very bad 
news for us. I was under the impression that XMI is XMI, and that one
should only encounter minor differences. By superstructure, do you
mean that an entirely different (and incompatble) meta-meta model
is used for UML serialised by MagicDraw, and for UML understood by
Eclipse?

I would have imagined both are compatible with standard MOF. Or is the 
problem purely in the XMI serialisation?

Either way, it's odd that Eclipse UML2 just crashes with 
OutOfMemoryError when I try to parse the file, instead of fail
with some sensible message.

Is our *only* hope really to write our own parser to transform
MagicDraw XMI to an XMI variant that Eclipse UML2 understands?


Vlad Varnica het geskryf:
> I think that Magic Draw is using MDR as UML Supertructure which is not 
> really compatible with EclipseUML 2. You have to manually write a parser 
> and then use other open source projects to transform it. This is not an 
> easy job !!! Note that Omondo did the same job two years ago by creating 
> a parser from UML 2.1/UML 2.2 to UML 2.0 which was AndroMDA compatible. 
> The estimated project was only 3 months for one full time developer and 
> the reality was 12 months for two engineers.
> We still have sometimes compatility problems and the job is never 
> perfect. The best is not to use MDR anymore and only select EclipseUML2 
> Superstructure like RSA, Borland, Omondo did it would make life easier :-)
> Good luck for your project.