On Fri, Apr 17, 2009 at 10:18, Rickard Öberg <[email protected]> wrote: > The most logical result I can think of is to refresh the underlying > EntityState and then *replay* the events that related specifically to that > Entity. > Example: > Load Entity 123 with x=1,y="Foo" > Change x->3 > Refresh 123. x had been changed to 5 and y to "Bar" > Replay events for 123 > Entity 123 now has state x=3 and y="Bar", i.e. the merge between the new > state and the updated local state. > User is happy and completes() UoW > In store that data is now: 123: x=3, y="Bar"
Shouldn't this be called merge? And this also seems dangerous as qi4j doesn't know whether auto-applying values are valid in all cases. How about associations? If the new state has some associations and the replay removed all associations? Another question is, how will the value be applied. Would it be via x().set() and y().set()? Regards, Edward Yakop _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
