That is correct. For performance reasons, element names and brief descriptions are stored in plugin.xmi (so the tree browser can load quickly without having to parse all elements for this information). The elements dot xml file is only created when content is entered in the rich text fields.
Cheers, Chris Chris Sibbald, Ph.D., P.Eng. Senior Systems Engineer Mobile: +1 (613) 266 - 5061 Fax: +1 (613) 739 - 4786 [email protected] "Maciel, Eduardo (Brazil R&D)" <[email protected]> Sent by: [email protected] 07/01/2009 06:00 PM Please respond to Eclipse Process Framework Project Developers List <[email protected]> To Eclipse Process Framework Project Developers List <[email protected]> cc Subject [epf-dev] RE: Problems related to finding the physical components If I´m not wrong, if there is no description or any other information in the task or role other than the name and the brief description, epf stores it only in plugin.xmi Maciel From: [email protected] [mailto:[email protected]] On Behalf Of Tom Viviano Sent: quarta-feira, 1 de julho de 2009 18:54 To: [email protected] Subject: [epf-dev] Problems related to finding the physical components I am using EPF to develop a new methodology. One of the challenges I am having is the inconsistency with which EPF stores Model Elements such as Roles and Tasks in the physical dot xmi files. I have entered about 20 tasks and half of them are stored in <taskname>.xmi files and half of them are stored in the plugin.xmi file. Same thing with roles and other element. Does anyone know what controls where the model stores the element’s xml and how to force them one way or the other? Thanks, Tom Infosys Technology Consulting [email protected] **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** _______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
<<image/gif>>
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
