Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312044 - Set object state to CONFLICT in CDOTransactionConflictEvent
Summary: Set object state to CONFLICT in CDOTransactionConflictEvent
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Martin Fluegge CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-07 08:10 EDT by Martin Fluegge CLA
Modified: 2010-06-29 09:21 EDT (History)
0 users

See Also:
stepper: documentation-

Attachments
Patch v1 (1.16 KB, patch)
2010-05-07 08:15 EDT, Martin Fluegge CLA 		no flags Details | Diff
View All 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 Martin Fluegge CLA 2010-05-07 08:10:15 EDT 
When recieving a CDOTransactionConflictEvent you can call getConflictingObject() to get the related object. At this point is not in state CONFLICT. This could be quite confusing, so we better should change this.
Comment 1 Martin Fluegge CLA 2010-05-07 08:15:50 EDT 
Created attachment 167456 [details]
Patch v1

This patch solves the problem.
Comment 2 Eike Stepper CLA 2010-05-07 14:55:32 EDT 
You didn't set the review flag, but go ahead and commit the patch ;-)
Comment 3 Martin Fluegge CLA 2010-05-07 16:17:34 EDT 
Darn. Seems that Mylyn tricked me again. I certainly set the review flag and this time did not get an error message from mylyn so I thought that the flag had been set. I'll better check this next time ;)

But anyway... Committed to HEAD :)
Comment 4 Eike Stepper CLA 2010-06-29 04:40:22 EDT 
Available in 3.0 GA:
http://download.eclipse.org/modeling/emf/cdo/updates/3.0-releases/