Quoting Niclas Hedhman <[email protected]>:
No, that doesn't sound like a good idea at all. Implicit Uow handling is outright evil and will cause more problems that it solves, I am sure. What we have been discussing is; Given an Entity instance, and a Value type implementing the same interfaces (which one exactly?) there should be a method either in Entity, the ValueBuilder or separate utility class, where I can retrieve a Value instance of such Entity. The problem revolves around "which interfaces" to use for all the internal states, especially how to handle associations.
Combine all the state-interfaces into one single proxy implementing them all? There might be some name-conflicts though then, if there are two interfaces with same property/asso/many-asso name. Maybe make a special "EntityValueState" with methods for getting properties/assos/many-assos by qualified name? This might help with the handling assos too.
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
