Hi Ronan, 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.
Bruce MacIsaac Manager RMC Method Content bmaci...@us.ibm.com 408-250-3037 (cell) From: Ronan Heracles <rherac...@yahoo.com> To: "epf-dev@eclipse.org" <epf-dev@eclipse.org>, Date: 01/09/2013 10:59 AM Subject: [epf-dev] Single XMI file Sent by: epf-dev-boun...@eclipse.org Dear EPF-Dev, In the EPFC Architecture Overview, there is the following explanation : "The 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, Ronan _______________________________________________ epf-dev mailing list epf-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________ epf-dev mailing list epf-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/epf-dev
