Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312247

Summary:	Make the behaviour of INVALID objects configurable
Product:	[Modeling] EMF	Reporter:	Eike Stepper <stepper>
Component:	cdo.core	Assignee:	Eike Stepper <stepper>
Status:	CLOSED FIXED	QA Contact:	Eike Stepper <stepper>
Severity:	enhancement
Priority:	P3	CC:	Thomas.Kowatsch, vroldanbet
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Eike Stepper

2010-05-10 08:52:56 EDT

Currently all access to INVALID objects (except equals/hashCode) throw an InvalidObjectException. This can be a problem, e.g., for databinding that keep handles to objects internally.

Comment 1 Eike Stepper

2010-05-10 08:55:25 EDT

I added new API:

CDOView.Options.setInvalidationPolicy(CDOInvalidationPolicy policy)

And new SPI:

public interface CDOInvalidationPolicy
{
  public static final CDOInvalidationPolicy DEFAULT = new CDOInvalidationPolicy()...
  public static final CDOInvalidationPolicy RELAXED = new CDOInvalidationPolicy()...

  public void handleInvalidation(CDOObject object);
  public void handleInvalidObject(CDOObject object);
}

Comment 2 Eike Stepper

2010-05-10 08:56:10 EDT

Committed to HEAD

Comment 3 Eike Stepper

2010-06-29 04:40:57 EDT

Available in 3.0 GA:
http://download.eclipse.org/modeling/emf/cdo/updates/3.0-releases/