On Sat, Nov 20, 2010 at 5:30 PM, Rickard Öberg <[email protected]> wrote:
> Is there any particular reason you don't only want to expose the top layer? > Normally it would only make sense to expose the application layer (through a > UI layer), so do you have an exception to that? If I have this in Qi4j, layer1.uses(layer2) layer1.uses(layer3) layer2.uses(layer3) layer3.uses(layer4) there is nothing particularly illegal about it, and life goes on as usual. Then assume that "layer1" is the layer outside of Qi4j, in which case the there is no way to 'express' this in the current Assembly, without introducing an additional set of services. I think what I looking for is a 'known' layer representing the outside world, so that the above then becomes; LayerAssembly.EXTERNAL.uses(layer2) LayerAssembly.EXTERNAL.layer1.uses(layer3) layer2.uses(layer3) layer3.uses(layer4) as this could then also prevent modules to be added to such layer, and the generic "exportServices" would know what to look for without additional configuration. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
