> AbstractEntityStoreMixin will be renamed to EntityTypeRegistryMixin so > that it is clear what it does and doesn't do. It will also be possible > to use it in an EntityStore not by subclassing it, but rather using it > as a separate Mixin accessed through "@This EntityStore registry". Much > cleaner. About the handling of props/assocs, yes, that can probably be > extracted out into helper classes. It's just a matter of finding the > patterns and refactoring it. So far there are already three Fragments > for EntityStore implementations (Concurrent change concern, EntityStore > change notification SideEffect and the EntityTypeRegistryMixin). I think > more and more functionality will be extracted out into Fragments as we > see patterns that are recurring in all the implementations. Which, after > all, is one of the big supposed bonuses with COP in the first place :-)
Well said :) Michael _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
