[CAY-797] Lifecycle callbacks *CallbackInterceptor concept introduces problems for testing equality of contexts

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0M2
• Component/s: Core Library
• Environment: 3.0-prerelease svn 523667
• Assignee: Andrus Adamchik
• Reporter: Lachlan Deck
• Created: 05/Jun/07 07:39
• Updated: 09/Nov/08 01:07
• Resolved: 29/Jul/07 21:11

Description

Say you create a callback intercepted context as described here (http://cayenne.apache.org/doc/lifecycle-callbacks.html), or as in my case created a subclass of ObjectContextCallbackInterceptor to wrap these concepts.

ObjectContext myContext = new CallbackInterceptedContext();
Object a = myContext.newObject(SomeClass.class);
Object b = myContext.newObject(SomeClass.class);

myContext.equals( a.getObjectContext() ); // false (unless I override equals to provide a better test)
a.getObjectContext().equals( myContext ); // false
a.getObjectContext() == myContext; // false
a.getObjectContext().equals( b.getObjectContext() ); // true

So this gets a little messy having to essentially test in the correct direction. Now, I understand why this occurs (because the CallbackIntercepting essentially provides a proxy context for the context it contains) but it seems to me that this leads to some difficulties like the above that could possibly be more easily overcome were both DataContext and CayenneContext to implement callback intercepting directly.

Thoughts?

Issue Links

• relates to: CAY-834 DataContext and DataDomain must support lifecycle callbacks out of the box without wrapping