Thanks for the clarification. So the problem is that the bundles you install programmatically are gone when you restart. Perhaps Pax Runner is removing them? (dunno much about it). At an abstract level there is a conflict where you want a declarative configuration but want to programmatically modify it. This is fine but there will come a time when these two conflict in some way. I mention this because it would be reasonable for a launcher to have a mode where it removed anything it did not install (i.e., declarative spec wins). I'm NOT saying this is what is happening to you, but just that it is something to think about in your system design.
Anyway, you might also look at how they are being installed programmatically. Is it that they are no longer installed? or just not started? Otherwise, perhaps it is a quirk of the implementations you are using and should be reported to them as a bug/question. Jeff On 2010-03-04, at 8:48 AM, David Conde wrote: > Hi Jeff, > > I expect from a launcher something which allows me to start my OSGI > application in a easy and fast way just configurating in a configuration > file. I have tried with Pax Runner and at least until this moment I could > not remain the bundles which were not installed by Pax Runner configuration > file but were installed by my InstallerBundleManager bundle by programming > across using BundleContext.install method, after restarting this launcher. > > I do not know why a OSGI feature like Remaining of installed bundles after > restarting the framework is not being performed if I launch Equinox by using > Pax Runner Launcher. Since it is a requirement for me that installed bundles > by programming remain installed after restarting I asked in this email list > about other options or launchers which can solve my problem and in order to > know if somebody who have used Pax Runner has faced with the same problem. > > I have done tests with Equinox via console and I have checked that the > installed bundles via programming remain after Equinox restarts, so I just > need a simple launcher that make easy all the installation proccess. > > Thank you in advance > > David > > > -----Mensaje original----- > De: [email protected] [mailto:[email protected]] > En nombre de Jeff McAffer > Enviado el: jueves, 04 de marzo de 2010 14:20 > Para: OSGi Developer Mail List > Asunto: Re: [osgi-dev] Osgi Launchers Question > > On 2010-03-04, at 7:58 AM, David Conde wrote: > >> Regarding my last question I was wrong when I wrote because I really meant > what was the most used Launcher (instead of bundle) by Equinox developers? > > I think this whole discussion really revolves around what you mean by > "launcher". What behavior or functionality are you expecting the "launcher" > to do. > > To answer your question directly about Equinox, Equinox comes with a native > executable (typically eclipse.exe or launcher.exe) that does all manner of > fancy stuff around splash screens, JVM discovery and invocation etc. It can > be branded with icons etc to match your product requirements. > > Installation of bundles can be done declaratively in the config.ini file > with not need for any additional bundles. > > If you are using the o.e.e.simpleconfigurator bundle, you can use the > bundles.info file for a bit easier management and manipulation > > If you want really sophisticated provisioning and installation facilities, > look at Equinox p2. > > If you are looking for embedding the framework in another Java environment > then there are calls you can do using the standard OSGi launching API. > > So, it really depends on exactly what you are hoping for. > > Jeff > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
