Hi David, You can make pax runner keeping its persistent state by using the --ups (use persistent state) option. (look at the options overview at [1])
However, you can also defere the execution of the readily made setup (core responsibility of pax runner) by using the --executor option. See [2]. [1] http://paxrunner.ops4j.org/display/paxrunner/Options+index and [2] http://paxrunner.ops4j.org/display/paxrunner/Executors HTH, Toni On Tue, Mar 9, 2010 at 11:24 AM, David Conde <dco...@citic.es> wrote: > Hi, > > > > I have used Pax Runner that I launch the OSGI framework works fine. But if > I restart Pax Runner the Bundles do not keep their state. For example if I > run a bundle which install another bundles from the pathfile this bundles > will not appear like installed bundles the next time I restart Pax Runner. > Is there any option or any way to launch the OSGI environment created by Pax > Runner without restarting all the bundles states? I mean there is anything > to call firstly Pax Runner in order to create the initial context with all > the bundles, and then launch this OSGI Context from other side different to > Pax Runner (since Pax Runner does not keep the bundles when it restart). > > > > Any idea? > > > > I guess somebody could have a problem similar?I mean people with many > bundles should use a Launcher but I guess there will be a way to launch this > OSGI context created by the Launcher in order to keep the Bundles state. > > > > Thank you in advance > > > David > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.com t...@okidokiteam.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software.
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
