Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361904 - [Legacy] URI clash and postCommit notifications
Summary: [Legacy] URI clash and postCommit notifications
Status: CLOSED WORKSFORME
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.legacy (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Christian Damus CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-25 06:44 EDT by Alex Lagarde CLA
Modified: 2013-10-24 08:05 EDT (History)
4 users (show)

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 Alex Lagarde CLA 2011-10-25 06:44:20 EDT 
This issue has been discussed in the following post : http://www.eclipse.org/forums/index.php/t/256386/ .

I've filed this ticket under cdo.core as I do not know if this issue is due to legacy mode or not.

You can find in the forum pust a very naive patch that simply order post-commit notifications by first notifying CDOResources and then all CDOObjects.

It main be cleanier to order notifications according to containment (first notify containers and then children).
Comment 1 Eike Stepper CLA 2011-10-25 06:52:35 EDT 
I talked to Martin and it looks like a legacy issue at a first glance. Let's see...
Comment 2 Alex Lagarde CLA 2011-10-25 06:55:48 EDT 
By taking a closer look at CDOLegacyWrapper, I strongly suspect that the issue is due to the call to revisionToInstanceResource() inside cdoResource() : as we get the OID of the CDOResource of a CDOLegacyWrapper that just have been updated, this returns OID4 although the "objects" map of the transaction still maps this resource with "oid1". 

That leads to the creation of a new Resource and hence the URI Clash issue.
Comment 3 Eike Stepper CLA 2012-06-05 07:28:26 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 4 Eike Stepper CLA 2012-08-14 22:50:14 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:05 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:15:54 EDT 
We'll try to address open problems in 4.3 (master) first and then port fixes back to 4.2.
Comment 7 Steve Monnier CLA 2013-10-24 05:02:24 EDT 
I can't reproduce the issue of the initial scenario on CDO 4.3. I guess you can close this one.
Comment 8 Eike Stepper CLA 2013-10-24 08:05:13 EDT 
Yes, we can reopen if needed.