Edward Yakop wrote:
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.
That's up to the user. But maybe separating the functionality into two would make sense: refresh() which only updates state and merge() which does refresh and then replay of events.
How about associations? If the new state has some associations and the replay removed all associations?
That's not possible. Remove association events are on individual basis only (i.e. there's no mass-removal like collection.clear()).
Another question is, how will the value be applied. Would it be via x().set() and y().set()?
It will be done on a low-level, so through EntityState.setProperty(). The high-level properties will then be reset so that access will call EntityState.getProperty().
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
