Hey, I'm implementing Qi4j using COP, but I'm not sure it's going to be good enough from a performance perspective, and the class explosion is immense. For some cases I'm going to KISS so that while there will be a Composite interface, with subinterfaces for the parts, the implementation is going to be a plain Java class which simply implements it all. So, instead of the onion architecture in the current design, and instead of the full Qi4j-thing that we discussed, I might make something in between. Not sure yet.
One of the main problems is the number of instances in each layer. Nr of models <= nr of resolutions <= nr of instances, so it doesn't really make sense to push it all together into one object. E.g. if all parts of the Composite are pushed into one then for each Composite there will be a number of instances which all have the exact same Model mixin. Not good. But the onion design going on currently doesn't work either. So... not sure what to do. Hm.... /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
