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

Bug 370665

Summary: optimize serialization mechanism
Product: [Modeling] MDT.RMF Reporter: Mark Broerkens <eclipse>
Component: Reqif-1.0Assignee: Mark Broerkens <eclipse>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: michael
Version: unspecified   
Target Milestone: i12.03   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Mark Broerkens CLA 2012-02-05 11:57:32 EST
the current mechanism for serializing the internal ReqIf model to XML makes use of an intermediate model to model transformation. Even though this transformation is very fast, it has some disadvantages:
* errors that might occur during deserialization need to be traced during the model to model transformation (this is not yet implemented and leads to unspecific error messages)
* during load and safe the complete model is transformed into a second model. This model is more complex than the original ReqIf meta model and thus additionally consumes at least the same amount of memory as the original model.
* During development the developer might accidentally choose the wrong resource or factory.
* the intermediate model to model transformation is very generic and works well for models that comply 100% to the ReqIf standard. However, in case of errors in the input model it is hard to identify the original source of an error during transformation. 

I do not expect too much effort for implementing a resource that is based on the ecore XMLResourceImpl and directly loads and safes the data without any intermediate transformation.
Comment 1 Michael Jastram CLA 2012-04-10 05:52:19 EDT
This is as good as resolved.  I leave it to Mark to resolve it.
Comment 2 Michael Jastram CLA 2012-04-12 10:44:48 EDT
I mark it as resolved to keep Bugzilla-Sanity