Community
Participate
Working Groups
Commit 1 adds a reference to object X. Commit 2 detaches X. Both can happen at the same time when the commits arrive at the server, so no client logic can detect and prevent this scenario.
Created attachment 170811 [details] Patch v1
Committed to HEAD
The boolean configuration property of the server to control this behaviour is IRepository.Props.ENSURE_REFERENTIAL_INTEGRITY = "ensureReferentialIntegrity". The same property is used to control the behaviour of bug 316434.
Available in 3.0 GA: http://download.eclipse.org/modeling/emf/cdo/updates/3.0-releases/
Created attachment 174963 [details] Testcase Testcase which shows that it is possible to lock detached target objects. I confirm to 1) The number of lines that you changed is smaller than 250. 2) You are the only author of these changed lines. 3) You apply the EPL to these changed lines.
Please reopen.
Reopening for investigation...
This is a 3.0 bug, can you please open a new one?
Opened bug 320690
Moving all open problem reports to 4.0
Closing.