Looks easy. Just do the stuff you normally do in bootstrapping an application.
Is the lifecycle of creating a new application on start and just passivating it on stop enough? Or must there be more, like suspending=passivate, and stopping=shutting down ? What would be interesting is to put the Composites, Services, MetaInfo etc. into the (xml) configuration of a generic OSGi bundle to let the user configure the stuff he wants and just start the generic bundle. But I think thats stuff for later. Michael Niclas Hedhman schrieb: > Gang, > > I have just committed the first cut of something resembling running > Qi4j on OSGi. > > Only the API, SPI, Bootstrap and Runtime modules has been made into Bundles. > > I also created a simple "osgitest" bundle that instantiate a Composite. > > My guess is that there are more classloader issues when we put it > test, and I will deal with that when/if it occurs. > > I will deploy my Qi4j Swing client on OSGi tomorrow, and I will report > back how that goes. > > > Cheers > Niclas > > _______________________________________________ > 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
