Are you talking only about Services? Would you mind explaining a little more what you mean by "available"? Would it be analogous to availability of services in OSGi, so would naturally map to the OSGi concept of availability?
=David On Nov 20, 2010, at 1:37 PM, Niclas Hedhman wrote: > Gang, > I am integrating CXF with Qi4j and also exposing Qi4j services as OSGi > services, and it is apparent that the Visibility concept is great, but > I now lack another 'layer'. > > So, IF I want to automate that a "Qi4j Service" is available by > default, similarly to a Qi4j Service being available to other > consumers based on Visibility, there is either; > > 1. A lacking 'layer' on top of the top layer, OR > 2. A Visibility type of 'external' > > The former seems more 'accurate' if one sees the entire Qi4j > application as a "layer", and the latter gives the ability to expose > services anywhere, which then seems to be contradictory to our meme > "only layers directly above can access"... > > Of course, I can bypass it all, but that is not the point. My point is > that I think we should have a visibility concept (not necessarily a > type) that reaches outside the Qi4j world. > > > Comparing with the importedService; In that case there is an > 'injection point' declared anywhere in the layer structure, so perhaps > my quest is taking the wrong approach. Since this would suggest that > we likewise would have a exportServiceWith() method on the > ServiceDeclaration, which can be replaced with a clunky combination of > metaInfo and Activatable... > > Any suggestion on a way forward in this area? > > 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 _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
