Gang, I have created a kind of "Qi4j Server"[1] using OSGi. In that process, I have found some smaller issues in the OSGi compatibility of Qi4j, and I would like to have them fixed fairly soon (before New Year). All the issues I have found are related to the Manifests, so I think I have 2 choices;
1. Branch 1.2, fix the headers and release a 1.2.1 (possibly with some additional bug fixes). 2. Push real hard for a 1.3, with reduced scope of what Rickard outlined a few days ago (which hasn't been JIRIZED yet). WDYT? [1] The basic idea is that we can deploy many independent Qi4j applications on each server instance. To do that, I have two types of bundles; application bundles and plugin bundles. Application bundles contains an XML file with description of modules, i.e. which module/layer, which assembler for that, and a list of plugins that the application needs. The plugin contains the same module descriptor and also a layer descriptor, building the application layers. So, when a bundle is loaded, the system looks for whether it is a plugin or a application. If plugin, just record the descriptors. If an application, get the plugin dependencies (may be transitive) build up the layers, create the modules, instantiate the Assemblers and bring it all together. On bundle.start() the activate() method is called. The plugins can easily bridge the Qi4j and OSGi world, for instance for shared resources (DB pools for instance). This will also be used for server monitoring, alerting, authorization and so on. 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
