Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358055 - CDOPushTransaction.isDirty() should call delegate.isDirty()
Summary: CDOPushTransaction.isDirty() should call delegate.isDirty()
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-19 02:36 EDT by Eike Stepper CLA
Modified: 2012-09-21 06:51 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eike Stepper CLA 2011-09-19 02:36:45 EDT
Cloned from: 357400: CDOPushTransaction.isDirty() should call delegate.isDirty()
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357400

Hi Everyone ! 

A minor bug that is very easy to work around : when using the new remote locking capabilities of CDO by opening a transaction using its durable locking ID, if I create a push transaction and import changes from a file, the following state occurs : pushTransaction.isDirty() return falses although pushTransaction.getDelegate().isDirty() returns true.

It seems raisonnable to add || delegate.isDirty() in the CDOPushTransaction.isDirty() method.


What do you think ?
Comment 1 Eike Stepper CLA 2011-09-19 02:43:39 EDT
Committed revision 9172:
- branches/4.0-maintenance/plugins/org.eclipse.emf.cdo
Comment 2 Eike Stepper CLA 2011-09-19 02:44:11 EDT
Resolved.

Unfortunately Indigo SR1 is almost out ;-(
Comment 3 Eike Stepper CLA 2012-09-21 06:51:55 EDT
Closing.