Michael Hunger wrote: > Sounds sensible altough I'd surely taken the other way round, perhaps > starting with one interface (perhaps with generics for the concept) and > only partioned it if needed.
Alright, that makes sense as it is right now. I'm gonna try it the other way round: Only have ApplicationModel,LayerModel,ModuleModel,CompositeModel, etc. and squeeze all the functionality of the other logical layers into this. The separation between model/resolution/binding/context is then mainly going to be how the code is structured is in this code (e.g. "bind()" is going to use model information in the same class). It's going to take some discipline to get this right, but it sure will make the codebase a heck of a lot smaller :-) /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
