Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342115 - export output xml, use name key instead of feature id in revision element
Summary: export output xml, use name key instead of feature id in revision element
Status: CLOSED WONTFIX
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 04:26 EDT by Nils Israel CLA
Modified: 2011-04-12 03:43 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nils Israel CLA 2011-04-07 04:26:18 EDT 
Build Identifier: 

<feature> elements nested inside the <revision> element refer to their EStructuralFeature by name, it might make sense to use a name key in the <revision> element for the containing feature, too

Reproducible: Always
Comment 1 Nils Israel CLA 2011-04-07 04:43:51 EDT 
This would simplify the process of exporting the repo, modifying the model und the exported file and reimporting it to support a kind of "model evolution"
Comment 2 Eike Stepper CLA 2011-04-12 03:43:51 EDT 
I apologize, when I asked you to submit this enhancement request I was not fully aware that the containingFeatureID only has a meaning in the context of the EClass of the containing EObject. Unfortunately this EClass is not known to the revision in question and calculating it by resolving the containerID is costly in both development terms and runtime performance (would at least double export and import times). The performance degradation could be controlled with an optional export/import config parameter, but still I see not enough benefit compared to the development cost.

I'm sorry but I won't fix for now.