Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325582 - [Legacy] DanglingReference on deleting legacy element
Summary: [Legacy] DanglingReference on deleting legacy element
Status: NEW
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.legacy (show other bugs)
Version: 4.13   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-17 09:04 EDT by Egidijus Vaisnora CLA
Modified: 2020-12-11 10:47 EST (History)
2 users (show)

See Also:


Attachments
test case attached (3.54 KB, text/plain)
2010-09-17 09:07 EDT, Egidijus Vaisnora CLA
no flags Details
A similar test case in legacy (4.07 KB, text/x-java)
2012-03-26 04:49 EDT, Esteban DUGUEPEROUX CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Egidijus Vaisnora CLA 2010-09-17 09:04:05 EDT
Exception:
org.eclipse.emf.cdo.util.CommitException: org.eclipse.emf.cdo.util.DanglingReferenceException: The object "CDOLegacyWrapper[null, org.eclipse.emf.cdo.tests.legacy.model1.impl.Product1Impl](org.eclipse.emf.internal.cdo.CDOLegacyAdapter)" is not contained in a resource
	at org.eclipse.emf.internal.cdo.transaction.CDOTransactionImpl.commit(CDOTransactionImpl.java:971)
	at org.eclipse.emf.internal.cdo.transaction.CDOTransactionImpl.commit(CDOTransactionImpl.java:982)
Comment 1 Egidijus Vaisnora CLA 2010-09-17 09:07:34 EDT
Created attachment 179109 [details]
test case attached
Comment 2 Egidijus Vaisnora CLA 2010-09-17 09:08:09 EDT
Scenario [Combined, MEMAudits, JVM, Legacy]
Comment 3 Esteban DUGUEPEROUX CLA 2012-03-26 04:49:08 EDT
Created attachment 213164 [details]
A similar test case in legacy

I have encoutered the same exception in legacy, it doesn't occurs if I use CDOSavepoint, I have encountered this issue in doing a undo of drag'n drop.
Comment 4 Eike Stepper CLA 2012-06-05 07:30:29 EDT
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems.

Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Comment 5 Eike Stepper CLA 2012-08-14 22:51:41 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 6 Eike Stepper CLA 2013-06-03 05:54:14 EDT
Hi Christian, I assign this legacy mode zilla to you, just in case you're ineterested. Don't feel obliged ;-)
Comment 7 Eike Stepper CLA 2013-06-29 12:17:39 EDT
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 8 Eike Stepper CLA 2015-07-14 02:10:34 EDT
Moving all open bugzillas to 4.5.
Comment 9 Eike Stepper CLA 2016-07-31 00:53:10 EDT
Moving all unaddressed bugzillas to 4.6.
Comment 10 Eike Stepper CLA 2017-12-28 01:15:39 EST
Moving all open bugs to 4.7
Comment 11 Eike Stepper CLA 2019-11-08 02:10:38 EST
Moving all unresolved issues to version 4.8-
Comment 12 Eike Stepper CLA 2019-12-13 12:55:23 EST
Moving all unresolved issues to version 4.9
Comment 13 Eike Stepper CLA 2020-12-11 10:47:14 EST
Moving to 4.13.