Niclas Hedhman wrote: > You see ValueComposites as DTOs, which I disagree with. There is > nothing inherent with Values that makes them "dumb value container", > and if we are to follow the general guideline, "Avoid Entities as much > as possible, and only introduce if the life cycle of it must be > tracked." then a vacuum arises and TransientComposite must be used > (which means complex persistence).
Ok, but even if you add methods to Values, there is still no real need, as far as I can tell, to have private state in Values. There *will* be an entity holding on to it (right???), which can do private things, if needed. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
