Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342115

Summary:	export output xml, use name key instead of feature id in revision element
Product:	[Modeling] EMF	Reporter:	Nils Israel <nils.israel>
Component:	cdo.core	Assignee:	Eike Stepper <stepper>
Status:	CLOSED WONTFIX	QA Contact:	Eike Stepper <stepper>
Severity:	enhancement
Priority:	P3
Version:	4.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Nils Israel

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

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

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.