I have spent a couple of days looking into guice-osgi (download from http://wiki.ops4j.org/confluence/display/ops4j/Guice-OSGi).
I find the proposed guice-osgi integration a bit invasive on both osgi and guice. For example, instead of: @Inject @OSGiService MyService unaryProxy; @Inject @OSGiService Iterable<MyService> multipleProxy; The consumer could just declare: @Inject MyService unaryProxy; @Inject Iterable<MyService> multipleProxy; if appropriate providers for the OSGi services are bound (just like the jndi integration works)...... I'm also not able to understand the advantages of using @OSGiServiceRegistration instead of the standard OSGi registration syntax.... (why tying the registration to an injection?) Best regards, Alessandro Mottadelli _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
