Hey, While refactoring the model I am sort of struggling with the different composite types (regular, entity and service for now). I have already separated services out from the other, so that internally there's a ServiceModel with an *optional* CompositeModel backing it, since it might be implemented without composites at all (e.g. importing a service through Jini).
Similarly, there are some significant differences between regular composites and entities. Only entities have associations, and the way these two handle state is radically different (regular composites always have the state in memory, whereas entities may have them lazy-loaded). I am currently not sure whether to make EntityModel as a subclass of CompositeModel, or whether I should try to separate them completely, or have a common baseclass, or what. My general thinking right now is that inheritance in general is a code smell, and it has worked so far. But I honestly don't know how to do with these two. Maybe I should just do something, and then y'all can look at it and say how to refactor it properly. Thoughts? We will most likely run into the same discussion later if we do ValueComposites, since they are again rather different from regular and entity composites. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
