Thank you for your answer.
I need a standard EMF XMI file because I want to use some EMF-based tools like Acceleo, to navigate in the model, generate from it, check rules, etc...
De : Bruce Macisaac <bmacisaa@xxxxxxxxxx>
À : Ronan Heracles <rheracles@xxxxxxxxx>; Eclipse Process Framework Project
Developers List <epf-dev@xxxxxxxxxxx>
Envoyé le : Mercredi 9 janvier 2013 21h23
Objet : Re: [epf-dev] Single XMI file
You can't store the method library in
a single XMI file.
These comments refer to how EMF was
used in the early development of EPF Composer to define an initial implementation
of the tool.
Is there any particular reason you want
the method library stored as a single file?
You can, of course, zip up a library
for purposes of sending it to others.
Manager RMC Method Content
Ronan Heracles <rheracles@xxxxxxxxx>
01/09/2013 10:59 AM
In the EPFC Architecture Overview,
there is the following explanation :
default EMF persistence implementation stores
a container and all containing elements, associated by composition, in
a single XMI file. Based on the above class diagram, this would produce
an extremely large XMI file that stores a method library and all its containing
elements. Naturally, this would lead to performance and scalability issues
as a method library grows in size. To resolve these issues, the default
EMF Ecore implementation is extended to optionally store the containing
elements in a separate XMI file. This design allows library elements such
as the method configurations, method plug-ins, method content description
and processes to be persisted in their own XMI files."
Please do you know how to desactivate
the multiple XMI files option, to store the method library in a single
XMI file ?
Thanks and best regards,
epf-dev mailing list