Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363613 - [Legacy] Importing resources can lead to omitted references
Summary: [Legacy] Importing resources can lead to omitted references
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.legacy (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-11 14:21 EST by Martin Fluegge CLA
Modified: 2020-12-11 10:47 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Fluegge CLA 2011-11-11 14:21:42 EST
Following this discussion (http://www.eclipse.org/forums/index.php/t/261795/) it seems that there is a problem when importing resource from a fiole system resource. When doing so references are not stored correctly. However, if the reference is then set using the generice CDOEditor, the reference is store. So the problem seems to be in the import functionality.

Ways to reproduce:
- create simple ecore with containment pattern
- create legacy aware transaction
- import resource and save
- look into the db-->the references are not stored
- set the reference in the editor and save
- look into the db-->the reference is stored
Comment 1 Eike Stepper CLA 2011-11-15 02:10:12 EST
Note for Martin: Can this bug be closed as invalid or duplicate of bug 363613?
Comment 2 Martin Fluegge CLA 2011-11-15 03:04:21 EST
(In reply to comment #1)
> Note for Martin: Can this bug be closed as invalid or duplicate of bug 363613?

Eike, you reference this bug. Which one did you mean as supposed duplicate?
Comment 3 Martin Fluegge CLA 2011-11-15 03:06:42 EST
Found it. Yes this one seems to be duplicate of bug 363661 and can be closed.
Comment 4 Eike Stepper CLA 2012-08-14 22:56:40 EDT
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 5 Eike Stepper CLA 2013-06-03 05:54:22 EDT
Hi Christian, I assign this legacy mode zilla to you, just in case you're ineterested. Don't feel obliged ;-)
Comment 6 Eike Stepper CLA 2013-06-29 12:18:01 EDT
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 7 Eike Stepper CLA 2015-07-14 02:19:41 EDT
Moving all open bugzillas to 4.5.
Comment 8 Eike Stepper CLA 2016-07-31 01:02:25 EDT
Moving all unaddressed bugzillas to 4.6.
Comment 9 Eike Stepper CLA 2017-12-28 01:21:13 EST
Moving all open bugs to 4.7
Comment 10 Eike Stepper CLA 2019-11-08 02:05:00 EST
Moving all unresolved issues to version 4.8-
Comment 11 Eike Stepper CLA 2019-12-13 12:47:02 EST
Moving all unresolved issues to version 4.9
Comment 12 Eike Stepper CLA 2020-12-11 10:47:56 EST
Moving to 4.13.