Hi David! I am not sure if I understood correctly your problem, but from what I understand you want to run pax-runner to start up equinox with a set of bundles (let's call it A). Then, one or more of those bundles will install other bundles (let's call them B). Now, if you terminate equinox and start it again with pax-runner, you want both A + B bundles to be started. If that is what you need, I think you can do the following (although I have not tested it). Every time you install a bundle on the fly (i.e. using another bundle), write a reference to that bundle in the runner/equinox/config.ini file (in the section "Client bundles to install"). Such reference should look like: reference:file:/C:/TEMP/com.springsource.slf4j.jcl_1.5.10....@3:start Hope this helps. Cheers, Humberto
On Tue, Mar 9, 2010 at 1:22 PM, David Conde <dco...@citic.es> wrote: > Hi Toni, > > > > I appreciate very much your help. > > > > I have tried both of them without right result. I have tried with --ups and > when I launch again Pax Runner all the bundles are installed and started by > default and any of them keep the previous state. I am using Equinox as > platform. > > > > If I type –executor=inProcess which is the option most close to my problem > I can not neither stop a bundle and the next time a close OSGI and open Pax > Runner again the bundle’s state is not keept. > > > > The problem is that I need something easy and fast to install a great set > of bundles for the first time by using Pax Runner, and then the next time I > want to use this context I would like to call another command or option > different to the Pax Runner default in which I can install new bundles and > keep them installed next time a launch OSGI. Is there any option to launch > OSGI framework after call Pax Runner in order to keep all the previous > installation? > > > > How do you face with this problem? > > > > Thank you in advance > > > > David > > > > *De:* tonit....@googlemail.com [mailto:tonit....@googlemail.com] *En > nombre de *Toni Menzel > *Enviado el:* martes, 09 de marzo de 2010 11:24 > *Para:* David Conde > *CC:* general@lists.ops4j.org > *Asunto:* Re: Option to launch OSGI framework after launching Pax Runner > > > > 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 > >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
