I'm very interested, but honestly don't think I'll have the time to look into this for at least several months.
=David On Nov 23, 2010, at 6:45 PM, Niclas Hedhman wrote: > Gang, > to what level is OSGi interesting to this current community? > > > I have just implemented a OSGiServiceExporter, a Qi4j service that > will export any visible Qi4j services that has a BundleContext as > metaInfo. The Qi4j service will be exported in OSGi under all > interfaces found (via Classes.interfacesOf() ). When the Qi4j > application is passivated, the services are unregistered in OSGi. All > is well. > > The OSGiImporter is not as straight forward. The ServiceImporter > implementation requires a OSGiImportInfo metaInfo containing one or > more Interfaces (together with BundleContext) to be looked for in > OSGi. It then create a ServiceTracker, which is also an > InvocationHandler for the declared imported Service interface, i.e. > the OSGi service will need to implement an interface that the > InvocationHandler can work on, and it won't be possible to cast it an > other type the service implements. It will therefor support that the > OSGi service disappears for a while (reloading for instance)... So far > so good. Problem is, there is no proper shutdown... :-( there is no > where to intercept the passivation of Qi4j in that case. Ideas are > welcome! > > > Ok, so back to my question... Shall I stick this in sandbox, or is > there sufficient interest to make it into library straight away?? > > > 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
